This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [v3] dejagnu support for simple cross compilers


> Date: Tue, 10 Apr 2001 16:23:16 -0700 (PDT)
> From: Benjamin Kosnik <bkoz@redhat.com>
> cc: gcc-patches@gcc.gnu.org, geoffk@redhat.com, rth@redhat.com
> 
> > > !         LIBS="${LIBS} -B${CROSS_LIB_PATH}/"
> > 
> > Please consider using $(FLAGS_FOR_TARGET) or some variant thereof.  It
> > will help finding crt0.o when it's built in libgloss, for example.
> 
> Hmm. I can't seem to get
> 
> FLAGS_FOR_TARGET
> CFLAGS_FOR_TARGET
> LIBCFLAGS_FOR_TARGET
> 
> to work. Any of them. 
> 
> FLAGS_FOR_TARGET is defined in the top-level Makefile of my x86-linux -x- 
> powerpc-eabism build directory as follows:
> 
> FLAGS_FOR_TARGET =  -nostdinc -B$$r/$(TARGET_SUBDIR)/newlib/ -isystem 
> $$r/$(TARGET_SUBDIR)/newlib/targ-include -isystem $$s/newlib/libc/include 
> -B$(build_tooldir)/bin/ -B$(build_tooldir)/lib/ -isystem 
> $(build_tooldir)/include -L$$r/ld
> 
> Looks encouraging, but it isn't passed down to target libs. Even if I add 
> it to BASE_FLAGS_TO_PASS in the toplevel Makefile, and AM_MAKEFLAGS in 
> libstdc++v3/Makefile.am.

It's passed down, I believe, as 'CFLAGS', as in target libs it is no
longer the flags for the "target" but flags for the host.  (The
libraries don't have a "target", anyway, because they are not
compilers or assemblers.)

-- 
- Geoffrey Keating <geoffk@geoffk.org>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]