Configuring linker flags while cross-compiling gdb

[Aaron Gaudio <agaudio at eng dot mc dot xerox dot com>]

Continuing with my adventure from last week, I am now trying to cross-
comile gdb to run on i386-pc-solaris2.10 and build on sparc-sun-
solaris2.10. 

I used the following configure line:

$ bash_cv_have_mbstate_t=yes ./configure --build sparc-sun-solaris2.8 --
host i386-pc-solaris2.10

This seems to get the correct compilers to use. However, when trying to
link, it is missing the correct rpath-link (where I have the x86 sysroot
to link system libraries), and it is also not linking in a required
library, libsocket (I get undefined symbols that manually adding -
lsocket to the link command fixes).

So, now I'm trying to figure out if there is a way to pass these by way
of option or environment variable to the top-level configure in a way
that they will cascade to the subdirectory configures and/or Makefiles.
Perusing the scripts in question, the top-level configure and
Makefile.in use a variable called "LDFLAGS_FOR_TARGET", and that seems
like the place to add a -R option or -W,l,--rpath-link to take care of
the rpath, however the gdb/configure and gdb/Makefile.in don't reference
this variable at all...

Can anyone offer any advise (or point me somewhere where this has
already been explained)?


-- 
Aaron Gaudio           agaudio @ eng.mc.xerox.com           585-422-6876

                  While life is yours, live joyously;
                None can escape Death's searching eye:
                When once this frame of ours they burn,
                   How shall it e'er again return?

Attachment: signature.asc
Description: This is a digitally signed message part