From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/thrift: fix build failure on bfin
Date: Sun, 22 Feb 2015 22:46:59 +0100 [thread overview]
Message-ID: <54EA4E53.6050401@openwide.fr> (raw)
In-Reply-To: <20150222222748.64849cf0@free-electrons.com>
Hi Thomas,
Le 22/02/2015 22:27, Thomas Petazzoni a ?crit :
> Dear Romain Naour,
>
> On Sun, 22 Feb 2015 22:25:06 +0100, Romain Naour wrote:
>> Libtool append the sysroot path (lt_sysroot) with the libdir value found in
>> the libstdc++.la file only with bfin toolchain.
>
> And to you know why ?
Not really...
I found a sed expression in ltmain.sh which seems to set libdir with libdir from libstdc++.la
"eval libdir=`$SED -n -e 's/^libdir=\(.*\)$/\1/p' $func_resolve_sysroot_result`"
Then the sysroot is appended right after that:
func_append newdependency_libs " ${lt_sysroot:+=}$libdir/$name"
So I tried to find from where the sed expression come from.
And I found lt_aix_libpath_sed in configure which is use to set lt_cv_aix_libpath__CXX.
"lt_cv_aix_libpath__CXX=`dump -H conftest$ac_exeext 2>/dev/null | $SED -n -e "$lt_aix_libpath_sed"`"
So I added lt_cv_aix_libpath__CXX in THRIFT_CONF_OPTS.
In not sure if we need to do that for other architecture/toolchain.
I hope this will further investigation.
Best regards,
Romain
>
> Thanks!
>
> Thomas
>
next prev parent reply other threads:[~2015-02-22 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 21:25 [Buildroot] [PATCH 1/2] package/thrift: fix build failure on bfin Romain Naour
2015-02-22 21:25 ` [Buildroot] [PATCH 2/2] package/thrift: remove tests Romain Naour
2015-02-22 21:27 ` [Buildroot] [PATCH 1/2] package/thrift: fix build failure on bfin Thomas Petazzoni
2015-02-22 21:46 ` Romain Naour [this message]
2015-02-23 23:39 ` Romain Naour
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=54EA4E53.6050401@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox