Subject: Re: USE_LIBTOOL and C++
To: Johnny C. Lam <firstname.lastname@example.org>
From: Nick Hudson <email@example.com>
Date: 06/21/2000 07:55:59
"Johnny C. Lam" wrote:
> Hubert Feyrer <firstname.lastname@example.org> writes:
> > On Tue, 20 Jun 2000, Johnny C. Lam wrote:
> > > Our old pkglibtool, which is apparently now deprecated, had a new
> > > option "--cplusplus" to link in cr++t.o with C++ libraries to ensure
> > > that global static contructors were called at the proper time. Is
> > > this no longer necessary? If not, then we can't change any of the C++
> > > library packages to USE_LIBTOOL, e.g. devel/boost, */kde*, x11/qt*.
> > Really, I'd expect g++ to care for handling cr++t.o. We don't have to deal
> > with crt.o as users (of the toolchain) either.
> I absolutely agree, but we still have to work around this problem for
> the 1.4.* and the upcoming 1.5 branch, as I don't recall anyone fixing
> this yet.
Doesn't 1.5 make this less of a problem as we have more ELF platforms.
> I was asking because I wanted to know if we should be pulling up the
> --cplusplus stuff in pkglibtool into libtool, or if we should just
> leave all the C++ packages to use pkglibtool for now.
I understand the problem now. I say we try and remove pkglibtool and
add back the cplusplus flag and make a libtool-1.3.5nb4. I can take a
look at doing this this evening.
> -- Johnny C. Lam <email@example.com>
> Department of Statistics, Carnegie Mellon University