While attempting to build libgfortran with the latest libtool I got the
following error:
if /bin/sh ./libtool --mode=compile
/proj/opensrc/sje/svn.libtool/build-ia64-hp-hpux11.23-trunk/obj_gcc/./gcc/xgcc
-B/proj/opensrc/sje/svn.libtool/build-ia64-hp-hpux11.23-trunk/obj_gcc/./gcc/
-B/proj/opensrc/sje/svn.libtool/gcc-ia64-hp-hpux11.23-trunk/ia64-hp-hpux11.23/bin/
-B/proj/opensrc/sje/svn.libtool/gcc-ia64-hp-hpux11.23-trunk/ia64-hp-hpux11.23/lib/
-isystem
/proj/opensrc/sje/svn.libtool/gcc-ia64-hp-hpux11.23-trunk/ia64-hp-hpux11.23/include
-isystem
/proj/opensrc/sje/svn.libtool/gcc-ia64-hp-hpux11.23-trunk/ia64-hp-hpux11.23/sys-include
-DHAVE_CONFIG_H -I. -I/proj/opensrc/sje/svn.libtool/src/trunk/libgfortran -I.
-iquote/proj/opensrc/sje/svn.libtool/src/trunk/libgfortran/io
-I/proj/opensrc/sje/svn.libtool/src/trunk/libgfortran/../gcc
-I/proj/opensrc/sje/svn.libtool/src/trunk/libgfortran/../gcc/config
-I../../.././gcc -D_GNU_SOURCE -std=gnu99 -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition -Wextra -Wwrite-strings -O2 -g
-mlp64 -MT backtrace.lo -M
D -MP -MF ".deps/backtrace.Tpo" -c -o backtrace.lo `test -f
'runtime/backtrace.c' || echo
'/proj/opensrc/sje/svn.libtool/src/trunk/libgfortran/'`runtime/backtrace.c; \
then mv -f ".deps/backtrace.Tpo" ".deps/backtrace.Plo"; else rm -f ".deps/backtr
ace.Tpo"; exit 1; fi
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
make[6]: *** [fmain.lo] Error 1
Now, obviously, what I want to do is add --tag=CC to the libtool call.
But I can't figure out where to do this. If I look at Makefile.in I see
where this is coming from but Makefile.in is generated from Makefile.am
so I shouldn't be editing Makefile.in. When I look at Makefile.am I
don't see how we got this compile line. What do I change to get
--tag=CC added to the libtool call?
The libstdc++-v3/src/Makefile has:
LTCXXCOMPILE = $(LIBTOOL) --tag CXX --mode=compile $(CXX) $(INCLUDES) \
$(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS)
But libgfortran doesn't have a line like this so how is it coming up
with this compile line?
Steve Ellcey
[EMAIL PROTECTED]
