From: ams AT ludd DOT luth DOT se (Martin Str|mberg)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: The DXE mechanism - has anybody used it effectively?
Date: 25 Dec 1998 18:17:38 GMT
Organization: University of Lulea, Sweden
Lines: 32
Message-ID: <760ks2$66e$1@news.luth.se>
References: <8D53104ECD0CD211AF4000A0C9D60AE337C6ED AT probe-2 DOT Acclaim-Euro DOT net> <zG6T+BAzLpg2EAn$@lwithers.demon.co.uk>
NNTP-Posting-Host: queeg.ludd.luth.se
X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Laurence Withers (lwithers AT lwithers DOT demon DOT co DOT uk) wrote:
: gcc -c a-dxe.cpp -o a-dxe.o
: dxegen a-dxe.dxe _test a-dxe.o
: ld -X -S -r -o dxe__tmp.o -LC:/PROGRAMS/DJGPP/lib a-dxe.o  -T dxe.ld 
: Error: input file has more than one section; use -M for map

Ho-hum... How does your DJGPP/LIB/DXE.LD look? One way to get past
this can be to have DXE.LD look like this:

----- start -----
OUTPUT_FORMAT("coff-go32")

FORCE_COMMON_ALLOCATION

SECTIONS {
  .text : {
    *(.text)
    *(.data)
    *(.bss)
    *(.eh_fram)
    *(COMMON)
  }
}
----- end -----

I have no idea how this affect C++ (I don't do C++), but this got me
past some troubles rebuilding libc or libm (forgotten which one).


Right,

							MartinS