Re: [PATCHv3 3/6] gcc: Statically link in support libraries e.g. libmpfr libgmp etc.

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Mon, 2011-03-14 at 10:52 -0700, Khem Raj wrote:
> On Sat, Mar 12, 2011 at 4:50 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > If you look at the way the SDK toolchain works in Poky, it automatically
> > ships the versions of these libraries that it needs so we don't actually
> > have this problem.
> >
> 
> Yes thats one way of doing it and if you got it working this is fine
> but there were issues when referencing
> due to ORIGIN mucking. So this was better and cleaner than we link in
> this libs into binary itself.

The $ORIGIN stuff should be working just fine, have you checked this?

>   From
> my POV even this solution can be improved by adding the support libs
> to gcc build itself as sources
> then we dont need to muck with gcc build configury at all. I have been
> doing that for non OE related
> SDKs and has been best so far.

As I mention above, I do think we have a solution for this which is
working...

> > Also, looking at the patch again, was the first LDFLAGS change meant to
> > be in there, is that related or different to the shared/static
> > mpfr/mpc/gmp issue?
> 
> LDFLAGS are modified to get the LDFLAGS into gcc itself otherwise it
> would not honour
> the modified LDFLAGS to pass -static option.

Hmm, I'll look at the patch again as that didn't seem to be the only
LDFLAGS change but I could be wrong.

Cheers,

Richard