This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gfortran+libcpp: linking objects from c-compiler
- From: Tom Tromey <tromey at redhat dot com>
- To: Daniel Franke <franke dot daniel at gmail dot com>
- Cc: fortran at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Tue, 15 Apr 2008 18:09:47 -0600
- Subject: Re: gfortran+libcpp: linking objects from c-compiler
- References: <200804152259.58360.franke.daniel@gmail.com>
- Reply-to: tromey at redhat dot com
>>>>> "Daniel" == Daniel Franke <franke.daniel@gmail.com> writes:
Daniel> Is it acceptable to simply link in the C-frontend object to
Daniel> gfortran (as C is a required language and the .o file will be
Daniel> available)? Do I need to do something else in addition or
Daniel> instead, like renaming or moving functions, pushing them to a
Daniel> library or anything else?
I think the usual rule is that c-* files are either specific to the C
front end, or in some cases, shared by the C family of front ends.
Perhaps this particular file could just be renamed and added to
libbackend.a.
This isn't completely ideal, because c-incpath.c refers to cpp_reader
and some front ends don't actually need libcpp ... but if I read the
Makefile correctly it looks like all the front ends already link to
libcpp, so maybe it isn't a big deal.
Tom