This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: question about -print-search-dirs
On 9/12/06, Daniel Jacobowitz <drow@false.org> wrote:
Looking at the original example, Kate, what exactly were you confused
about? If it was the "/../lib64" suffix, those are added _after_ the
list of directories to search are decided. They're added when we
consider whether the user asked for -m32 or -m64 (see multilib in the
documentation).
Much thanks for the explanation. This is precisely what was confusing
me.
Is there a gcc debug option (or another way) to determine if gcc is
defaulting to -m32 or -m64 mode? Or what I really want, the _actual_
search libraries - with "/../lib64" if in -m64 mode?
The reason I ask is that libtool (or more precisely the m4 macro
AC_LIBTOOL_SYS_DYNAMIC_LINKER in libtool.m4) uses
"gcc -print-search-dirs" to set sys_lib_search_path_spec. But
if gcc is in -m64 mode but -print-search-dirs is only listing -m32
libraries, then bad things happen later on.
Kate Minola
University of Maryland, College Park