libgcj versus libtool

Tom Tromey tromey@cygnus.com
Tue Jun 29 10:01:00 GMT 1999


>>>>> "Alexandre" == Alexandre Oliva <oliva@dcc.unicamp.br> writes:

Alexandre> libgcj can't currently be built before egcs is installed,
Alexandre> because libtool won't pass -B flags to xgcc.  This can't be
Alexandre> fixed in the current libtool for various reasons, so I've
Alexandre> come up with the attached patch to allow libtool-dependent
Alexandre> target packages to use an uninstalled egcs, in the same
Alexandre> build tree.

In the Cygnus tree we use a short patch to libtool instead.  This
works everywhere that libtool works.

I don't like the idea that I have to remember if a directory uses
libtool in order to figure out the target name.  I guess we could add
new targets to handle that though:

	all-target-libgcj: all-lt-target-libgcj

(People here do use these targets regularly.)

Alexandre> There is a minor problem: on platforms that do not support
Alexandre> running scripts directly (i.e., require /bin/sh
Alexandre> /path/to/script), this work-around won't work.  But then,
Alexandre> it will only be used to build libgcj, which doesn't build
Alexandre> on so many platforms anyway.

But it is a bug that will have to be fixed someday, right?  libgcj
will eventually be ported.

Alexandre> Since we've had a recent effort to allow gcc 2.95 and
Alexandre> libgcj to be built together, I'd like to have this patch
Alexandre> installed for gcc 2.95, to complete this effort.

I'm glad that Jeff put in the patches to do this, but I don't think
this is a supported mode.  It isn't something we advertise on the
libgcj web page, for instance.

Tom


More information about the Gcc-patches mailing list