From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/pkg-autotools: don't use config.site when cross-compiling
Date: Thu, 21 Aug 2014 23:50:41 +0200 [thread overview]
Message-ID: <53F669B1.505@openwide.fr> (raw)
In-Reply-To: <20140821163213.65ee473e@core2quad.morethan.org>
Hi Mike,
Le 21/08/2014 23:32, Mike Zick a ?crit :
> On Thu, 21 Aug 2014 23:19:12 +0200
> Romain Naour <romain.naour@openwide.fr> wrote:
>
>> Hi Thomas,
>>
>> Le 21/08/2014 22:06, Thomas De Schampheleire a ?crit :
>>> Hi Romain,
>>>
>>> On Tue, Aug 19, 2014 at 12:50 AM, Romain Naour
>>> <romain.naour@openwide.fr> wrote:
>>>> On fedora 20 64bits host, the file /usr/share/config.site contains
>>>> a fix for installing libraries into /lib/lib64 on 64bits systems
>>>> that redefine libdir in the generated Makefile
>>>>
>>>> For safety, disable loading this file when running the configure
>>>> script for the target and the host.
>>>>
>>>> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
>>>> ---
>>>> package/pkg-autotools.mk | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/package/pkg-autotools.mk b/package/pkg-autotools.mk
>>>> index bcc648d..cdc31bf 100644
>>>> --- a/package/pkg-autotools.mk
>>>> +++ b/package/pkg-autotools.mk
>>>> @@ -126,6 +126,7 @@ define $(2)_CONFIGURE_CMDS
>>>> $$(TARGET_CONFIGURE_OPTS) \
>>>> $$(TARGET_CONFIGURE_ARGS) \
>>>> $$($$(PKG)_CONF_ENV) \
>>>> + CONFIG_SITE="no" \
>>>> ./configure \
>>>> --target=$$(GNU_TARGET_NAME) \
>>>> --host=$$(GNU_TARGET_NAME) \
>>>> @@ -159,6 +160,7 @@ define $(2)_CONFIGURE_CMDS
>>>> CFLAGS="$$(HOST_CFLAGS)" \
>>>> LDFLAGS="$$(HOST_LDFLAGS)" \
>>>> $$($$(PKG)_CONF_ENV) \
>>>> + CONFIG_SITE="no" \
>>>> ./configure \
>>>> --prefix="$$(HOST_DIR)/usr" \
>>>> --sysconfdir="$$(HOST_DIR)/etc" \
>>>
>>> The autoconf documentation does not specify 'no' as a magic value,
>>> which means that the accidental presence of a file called 'no' would
>>> pick up the file.
>>> Wouldn't it be safer/cleaner to use CONFIG_SITE=/dev/null?
>>> Note that I have not tested if this actually works, just a thought.
>>
>> I tried with CONFIG_SITE="/dev/null" at first but I had
>> configure: loading site script /dev/null
>>
>> I may use THIS_IS_NOT_YOUR_CONFIG_SITE instead :)
>>
>
> Let me guess, that would result in something like:
> configure: site script THIS_IS_NOT_YOUR_CONFIG_SITE not found
No, there is no print at all.
>
>> So, I'm ok to keep "/dev/null" if you want.
>>
>
> If we where voting, I think the:
> configure: loading site script /dev/null
>
> is a much better message ans a person can even figure it out.
Thanks for voting.
Best regards,
Romain
>
> Mike
>> Thanks for review.
>> Romain
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2014-08-21 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 22:50 [Buildroot] [PATCH 1/2] package/pkg-autotools: don't use config.site when cross-compiling Romain Naour
2014-08-18 22:50 ` [Buildroot] [PATCH 2/2] Revert "package/localedef: don't use config.site when cross-compiling" Romain Naour
2014-08-21 20:06 ` [Buildroot] [PATCH 1/2] package/pkg-autotools: don't use config.site when cross-compiling Thomas De Schampheleire
2014-08-21 21:19 ` Romain Naour
2014-08-21 21:32 ` Mike Zick
2014-08-21 21:50 ` Romain Naour [this message]
2014-08-22 7:17 ` Thomas De Schampheleire
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=53F669B1.505@openwide.fr \
--to=romain.naour@openwide.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.