lockfile-progs: use correct CFLAGS
Use the correct CFLAGS from BR and not just the LDFLAGS. This is especially important for external toolchain setups, but the lockfile-progs buildsystem also hardcodes -Werror, which breaks the build in certain setups. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
This commit is contained in:
parent
bc065596b4
commit
a4bba08343
4
CHANGES
4
CHANGES
@ -2,8 +2,8 @@
|
|||||||
|
|
||||||
Fixes all over the tree.
|
Fixes all over the tree.
|
||||||
|
|
||||||
Updated/fixed packages: coreutils, hal, libcap, ncftp,
|
Updated/fixed packages: coreutils, hal, libcap,
|
||||||
xserver_xorg-server
|
lockfile-progs, ncftp, xserver_xorg-server
|
||||||
|
|
||||||
Issues resolved (http://bugs.uclibc.org):
|
Issues resolved (http://bugs.uclibc.org):
|
||||||
|
|
||||||
|
@ -21,7 +21,7 @@ $(LOCKFILE_PROGS_DIR)/.unpacked: $(DL_DIR)/$(LOCKFILE_PROGS_SOURCE)
|
|||||||
touch $(LOCKFILE_PROGS_DIR)/.unpacked
|
touch $(LOCKFILE_PROGS_DIR)/.unpacked
|
||||||
|
|
||||||
$(TARGET_DIR)/$(LOCKFILE_PROGS_BINARY): $(LOCKFILE_PROGS_DIR)/.unpacked
|
$(TARGET_DIR)/$(LOCKFILE_PROGS_BINARY): $(LOCKFILE_PROGS_DIR)/.unpacked
|
||||||
$(MAKE) $(TARGET_CONFIGURE_OPTS) LDFLAGS="$(TARGET_LDFLAGS)" \
|
$(MAKE) $(TARGET_CONFIGURE_OPTS) $(TARGET_CONFIGURE_ENV) \
|
||||||
-C $(LOCKFILE_PROGS_DIR)
|
-C $(LOCKFILE_PROGS_DIR)
|
||||||
cp -a $(LOCKFILE_PROGS_DIR)/bin/lockfile* $(TARGET_DIR)/usr/bin
|
cp -a $(LOCKFILE_PROGS_DIR)/bin/lockfile* $(TARGET_DIR)/usr/bin
|
||||||
$(STRIPCMD) $(STRIP_STRIP_UNNEEDED) $(TARGET_DIR)/$(LOCKFILE_PROGS_BINARY)
|
$(STRIPCMD) $(STRIP_STRIP_UNNEEDED) $(TARGET_DIR)/$(LOCKFILE_PROGS_BINARY)
|
||||||
|
Loading…
Reference in New Issue
Block a user