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] |
Ok, this is driving me nuts.
I've got a package (Konq/E) that I've been working on, fixed or stubbed all the current bugs, and now I'm down at the linking stage.
I get errors trying to link to the host's libraries (/usr/lib/...), that they aren't the right endianness, etc... typical couldn't-find-target-libraries error.
I've done this quite a few times before with other packages, and know that there is some finagling to let configure know what include and library paths to use.
1.) prefix refers to a place in which $prefix/lib has libraries for the target platform
2.) ditto for buildprefix
3.) I also pass --with-extra-libs pointing to a place with the libraries for the target platform reside.
What am I doing wrong?
Can someone give me a list of all the various ways,places, etc that autoconf/configure looks for using include paths?
Oh, and I do indeed see a correct -L argument to the failing g++ command... Someone mentioned that it might have something to do with the libtool archive files. Can someone explain this to me?
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe at sources dot redhat dot com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |