From: aldot at uclibc.org <aldot@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/bash
Date: Fri, 6 Apr 2007 04:55:38 -0700 (PDT) [thread overview]
Message-ID: <20070406115538.40286485FC@busybox.net> (raw)
Author: aldot
Date: 2007-04-06 04:55:37 -0700 (Fri, 06 Apr 2007)
New Revision: 18347
Log:
- using target's LDFLAGS as LDFLAGS_FOR_BUILD is b0rked
Modified:
trunk/buildroot/package/bash/bash.mk
Changeset:
Modified: trunk/buildroot/package/bash/bash.mk
===================================================================
--- trunk/buildroot/package/bash/bash.mk 2007-04-06 10:41:05 UTC (rev 18346)
+++ trunk/buildroot/package/bash/bash.mk 2007-04-06 11:55:37 UTC (rev 18347)
@@ -23,6 +23,8 @@
# This is broken when -lintl is added to LIBS
$(SED) 's,LIBS_FOR_BUILD =.*,LIBS_FOR_BUILD =,g' \
$(BASH_DIR)/builtins/Makefile.in
+ # using target's LDFLAGS as LDFLAGS_FOR_BUILD is b0rked
+ -$(SED) '/^LDFLAGS_FOR_BUILD/d' $(BASH_DIR)/{,*/{,*/}}Makefile.in
$(CONFIG_UPDATE) $(BASH_DIR)/support
touch $@
@@ -32,6 +34,7 @@
$(TARGET_CONFIGURE_OPTS) \
CFLAGS="$(TARGET_CFLAGS)" \
LDFLAGS="$(TARGET_LDFLAGS)" \
+ CCFLAGS_FOR_BUILD="$(HOST_CFLAGS)" \
ac_cv_func_setvbuf_reversed=no \
./configure \
--target=$(GNU_TARGET_NAME) \
next reply other threads:[~2007-04-06 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 11:55 aldot at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-06 19:09 [Buildroot] svn commit: trunk/buildroot/package/bash wberrier at uclibc.org
2008-05-01 19:07 nkukard at uclibc.org
2008-04-29 20:03 nkukard at uclibc.org
2008-03-11 18:12 ninevoltz at uclibc.org
2007-10-07 18:23 aldot at uclibc.org
2007-08-22 9:41 ulf at uclibc.org
2007-08-22 9:29 ulf at uclibc.org
2007-08-11 23:57 ulf at uclibc.org
2007-07-11 13:55 ulf at uclibc.org
2007-06-25 11:22 aldot at uclibc.org
2007-06-25 11:17 aldot at uclibc.org
2007-02-16 13:11 aldot at uclibc.org
2006-12-08 12:50 aldot at uclibc.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070406115538.40286485FC@busybox.net \
--to=aldot@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox