This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wed, Oct 06, 2004 at 06:36:20PM +0000, Alexander Povolotsky wrote: > > powerpc-linux-gcc-3.3.2 -o try -O2 -DPERL_USE_SAFE_PUTENV -I/usr/local > nclude -L/usr/local/lib try.c -lgdbm -lcrypt -lgdbm_compat > ./try > > and I got the following output: > > /usr/local/lib/gcc-lib/powerpc-linux/3.3.2/../../../../powerpc-linux/bin/ld: c > not find -lgdbm > collect2: ld returned 1 exit status > I can't compile the test program. > (The supplied flags or libraries might be incorrect.) Not to mention that once you fix the compiler invocation such that it does compile the test program, you'll error out one line later as the configurator tries to run the newly compiled ./try (which in this case will be a PPC binary, when the build host is not a PPC system). Hence the problem with cross-compiling PERL. It expects to be able to run executables it's built for the target system on the build system. That's going to be much tougher to work around than your library search path issue. -----Carl ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |