[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    [PATCH 0/3] (Re-)instate some build guards
From:       Johannes Schindelin <johannes.schindelin () gmx ! de>
Date:       2017-07-14 14:11:38
Message-ID: cover.1500041469.git.johannes.schindelin () gmx ! de
[Download RAW message or body]

It would appear that some compile-time flags are used as if they were
runtime flags, i.e. they are used in if (...) constructs, not in
`#if ... #endif` guards.

The effect *should* be the same, except when switching off optimization
(e.g. for debugging) where dead code is not removed, possibly leading to
build errors where features are disabled because the required functions
are unavailable.


Johannes Schindelin (3):
  copyfd: reinstate proper guard around munmap()
  inet_common: handle FEATURE_ETC_NETWORKS as a compile-time flag
  ash: use JOBS as the compile time option it actually is

 libbb/copyfd.c      |  2 ++
 libbb/inet_common.c |  5 ++++-
 shell/ash.c         | 12 +++++++++---
 3 files changed, 15 insertions(+), 4 deletions(-)


base-commit: a03ac6067764549f4ae25f9a34e1ee9b0d2bb4f2
Published-As: https://github.com/dscho/busybox-w32/releases/tag/busybox-build-guards-v1
Fetch-It-Via: git fetch https://github.com/dscho/busybox-w32 busybox-build-guards-v1
-- 
2.13.3.windows.1.13.gaf0c2223da0

_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]