From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: i686-pc-msdosdjgpp-g++ problems (long)
Date: 8 Nov 2002 09:24:51 GMT
Organization: Ericsson Erisoft AB, Sweden
Lines: 61
Message-ID: <aqfvt3$6t$1@antares.lu.erisoft.se>
References: <lrplsuounbjm9n878rvu4e4sobqofcu437 AT 4ax DOT com>
NNTP-Posting-Host: lws256.lu.erisoft.se
X-Newsreader: TIN [version 1.2 PL2]
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Charles Wilkins (chas AT pcscs DOT com) wrote:
...
: I fixed the links and was able to rebuild successfully, but when I
: tried to compile using i686-pc-msdosdjgpp-g++ I could not because the
: linker was looking for libstdcxx.a and all that was there was
: libstdc++.a.  So I made a link from libstdc++.a to libstdcxx.a to
: satisfy the linker.

: I am not sure I should have had to do this...
: Why is the linker looking for cxx and not c++ ?

Because "+" isn't a valid character in filenames in plain DOZE. So
DJGPP's libstdc++.a is named libstdcxx.a. What you did here seems most
appropriate.

: So after copying the ~config/os/djgpp headers into ~config/os/newlib
: directory,  libstdc++-v3 built and installed with no errors. I was
: able to then compile a binary using i686-pc-msdosdjgpp-g++ without
: error, but when I try to execute the binary under win98 or win2kpro, i
: get this:

: Exiting due to signal SIGSEGV
: General Protection Fault at eip=0001a11f
: eax=00000000 ebx=0003eb58 ecx=0003eb58 edx=007cffa0 esi=00000054
: edi=00001630
: ebp=007cff68 esp=007cff64
: program=H:\ROOT\PROJECTS\CPP\TEST\WELCOME.EXE
: cs: sel=01a7  base=01670000  limit=007dffff
: ds: sel=01af  base=01670000  limit=007dffff
: es: sel=01af  base=01670000  limit=007dffff
: fs: sel=017f  base=00005870  limit=0000ffff
: gs: sel=01bf  base=00000000  limit=0010ffff
: ss: sel=01af  base=01670000  limit=007dffff
: App stack: [007d0000..00750000]  Exceptn stack: [00042c88..00040d48]

: Call frame traceback EIPs:
:   0x0001a11f
:   0x0001a36e
:   0x0000167e
:   0x0000d1f8

And what does symify and bfdsymify say when run here?

: Note: the binary file size for this simple cpp program is 1,847,862
: bytes.

: Aside from not even executing properly, does this file size seem
: right?

Looks a little large, but so what? Probably multum debug info or
something. I suggest you ignore the size issue for now.

: Any ideas what is happening here?

Looks good. You managed to compile your program... Now you just have
some minor details to work out...


Right,

						MartinS