Heh, then I guess we need to list libstdc++ as a bootstrap requirement after all... (blush)
Michael -- [EMAIL PROTECTED] Development Team, Application Services Cable & Wireless Deutschland GmbH On Fri, Mar 08, 2002 at 04:40:01PM +0100, Christoph Schug wrote: > On Fri, 8 Mar 2002, Michael Schloh von Bennewitz wrote: >> If an OpenPKG user chooses to install the jdk-sun OpenPKG package (or another >> that depends on libstdc++), then she first has to install the libstdc++ >> package (which we don't have yet). The real question is, does jdk-sun depend >> on libstdc++? If so, then we need to make a new libstdc++ package, right? If >> so, then this doesn't belong with the other requirements information regarding >> how to bootstrap OpenPKG. > > jdk-sun is based in JDK package from Sun which is available binary only > (truely said there's also a source package but this requires existing JDK > in order to build). Since this binary is linked against an old libstdc++ > library. and we are forced to use a vendor package instead a own one. > Furthermore we even don't have any version of libstdc++ as a OpenPKG > package and I doubt that we want to have one. > > In case you really want to have a libstdc++ package we would need > different ones links against different versions of glibc. Furhtermore > these libs are required to be dynamically linked. This is not just a can > of worms (as Ralf would call it :-). This would be *real* nightmare.
msg00063/pgp00000.pgp
Description: PGP signature
