On Mon, Jan 23, 2006 at 12:13:50AM +0000, Nick Glencross wrote: > Nick Glencross wrote: > > >There seem to be a few recent events which can now trigger a newish > >problem: > > > <snip> > > >The real problem is that -L/usr/local/lib is brought in from parrot, > >so we have a few choices: > > > > * Just remove -Ls brought in from 'lddflags', which seems safe to > >me, or > > * remove the -L and add it to another config var, or > > * rearrange the flags in root.in so that LINKFLAGS is after > >ALL_PARROT_LIBS > > I've attached two patches, one does the first, and the other the 3rd. > > Both should solve the problem; so it probably comes down to aesthetics. > I prefer just removing -Ls, and if any problems are encountered, > introduce them later in linking (as with ICU).
I prefer #1 over #3 as #3 would prevent any ldflags being used for the linkage to libparrot. There is also a fourth option of simply not pulling in 'lddflags' from Perl. This would mean setting ldflags as a per platform hints but I think this may be the better long term option. Thoughts? -J --
pgpmbvsHNvTG3.pgp
Description: PGP signature
