[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gobolinux-devel
Subject:    [gobolinux-devel] Re: Linux 2.6.15.1 Recipe
From:       lucasvr () lsi ! usp ! br (Lucas Correia Villa Real)
Date:       2006-01-23 13:42:13
Message-ID: 200601231040.02410.lucasvr () lsi ! usp ! br
[Download RAW message or body]

On Monday 23 January 2006 03:44, Jonas Karlsson wrote:
> On Mon, 23 Jan 2006 02:54:48 +0100, Hisham Muhammad <hisham.hm@gmail.com>
>
> wrote:
> > On 1/22/06, Lucas Correia Villa Real <lucasvr@gobolinux.org> wrote:
> >> Another problem is that compiling against /Programs and union
> >> mounting it ends making the application use the host's .la and .pc
> >> files, linking with the wrong libraries. And, in this case, no
> >> FixLibtoolLa could be
> >> executed at the cross-compiled app, as it would hardcode the
> >> host's /System/Links directory.
> >
> > Oh, I see. At first I did not understand it. You mean that the
> > crosscompiled .la and .pc files point to /Programs and further
> > compilations will follow them and end up grabbing files from the host.
> > So it's the same problem as idea #2. And a big problem that is
> > (libtool and pkgconfig are only two, think of the other weird stuff
> > that can show up with these same assumptions).
> >
> >> I don't know, maybe it's suitable to union-mount every app
> >> from /ARM/Programs.. what do you think?
>
> I dont think it's necesary to union mount every program, but only to
> mount /ARM at /, shadowing the standard files at the host. This could be
> done at Compile and would solve the problem of paths in .la and.pc files.

If we're going towards this solution, the host's appversions cannot match 
the target's versions.. I'll pay more attention to this problem today.

-- 
Lucas
powered by /dev/dsp

[prev in list] [next in list] [prev in thread] [next in thread]