Daniel Macks wrote:
> Look for where the bad .la file gets created. There's probably a
> libtool command in the build output that does "-o libstdc++.la". Look
> at that libtool command and the compiler command after it, see if they
> have any -L flags that point to the build dir (either absolute
>
Look for where the bad .la file gets created. There's probably a
libtool command in the build output that does "-o libstdc++.la". Look
at that libtool command and the compiler command after it, see if they
have any -L flags that point to the build dir (either absolute
-L/sw/src/whatever or relative
I tried all the possible fixes suggested there or looked for the
problem. I could not fix the warning though. Could be some vague thing
related to point no. 3 made in that wiki-page.
On 5 Feb 2008, at 15:40, Alexander K. Hansen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> It's n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's nothing specific to cross-compilers. The issue is talked about on
http://wiki.finkproject.org/index.php/Fink:Porting_Notes, in theCommon
Libtool Linking Problems section, item 2.
Murali Vadivelu wrote:
| Dear All,
|
| Sorry for the post. I ha
Dear All,
Sorry for the post. I have fixed it. It was a minor trouble with
symlinks!
Btw, I am trying to create a cross-compiler, i386-elf-gcc. Everything
goes well, except for this fink validate warning:
$ fink validate /sw/fink/10.5/local/main/binary-darwin-i386/devel/i386-
elf-gcc_3.4.6
