From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: i686-pc-msdosdjgpp-g++ problems (long) Date: 11 Nov 2002 17:45:59 GMT Organization: Aachen University of Technology (RWTH) Lines: 22 Message-ID: References: <1036779663 DOT 158618 AT queeg DOT ludd DOT luth DOT se> <1h6osuka51oan46817ptm2o1loq3k6fqm7 AT 4ax DOT com> <200211082039 DOT gA8Kdck00835 AT envy DOT delorie DOT com> <1036845028 DOT 195290 AT queeg DOT ludd DOT luth DOT se> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1037036759 17179 137.226.32.75 (11 Nov 2002 17:45:59 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 11 Nov 2002 17:45:59 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Charles Wilkins wrote: >>The problem is somewhere between the DJGPP runtime and the libstdc++. > I agree. >>But there is not really such a thing as a libstdc++ "hosted" >>somewhere. It's essentially just stored on Linux, but has no other >>links to that platform. The .a file should usually be identical to >>one built natively using DJGPP itself (or to the pre-built one). > In my case, the libstdc++.a is significantly larger than the native > build libstdc++.a Absolute overall filesize may not make much sense. Be sure to check the 'size libstdc++.a' outputs, in particular the .text segment sizes reported for the individual .o files in the lib, before you draw any conclusions. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.