From: Andy Ross <andy.ross@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-4.7: Add fix for libtool rpath problems
Date: Fri, 24 Aug 2012 08:53:16 -0700 [thread overview]
Message-ID: <5037A36C.8020401@windriver.com> (raw)
In-Reply-To: <1345817543.14369.70.camel@ted>
On 08/24/2012 07:12 AM, Richard Purdie wrote:
> This avoids problems with libstdc++ having bad rpaths (/usr/lib/../.lib)
> in its .la file. See the patch for more information.
Heh, I was just sitting down having discovered the same thing. Isn't
the root cause at least partially that gcc is using a different
libtool implementation than the rest of the build? I note it's also
missing the normalization patches that went into the standard libtool
(though that's benign here as -rpath isn't used).
Andy
next prev parent reply other threads:[~2012-08-24 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 14:12 [PATCH] gcc-4.7: Add fix for libtool rpath problems Richard Purdie
2012-08-24 14:57 ` Khem Raj
2012-08-24 15:29 ` Richard Purdie
2012-08-24 16:38 ` Khem Raj
2012-08-24 15:53 ` Andy Ross [this message]
2012-08-24 16:19 ` Richard Purdie
2012-08-24 16:29 ` Andy Ross
2012-08-24 16:37 ` Khem Raj
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=5037A36C.8020401@windriver.com \
--to=andy.ross@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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.