X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
        bh=qBfz3tZ1944XpBttA+kX+6/rEWiMdNvuqe4EQMwssok=;
        b=JShWKrUsJzAEV2fLcmZG2Dh4eUS05iNCTipr9ws5QlBJIxGk0bCJhdw5cQ6wEvDTr5
         3bxQCMpMhjAUlDtIASAwKK+Vnv3RTAL+gQcG26hVWAB6FgEcvrz411TZ4gB/2WlEltN4
         dgB1Wc/DFopFMTSu5b1HZ7sdKzTZgvdUS7SR8ItKal72Zsu/7wyhb7ilMoQiW2gfFz4r
         iJKlQykUyZaxAmBN5pr6K64/R1kV7Zl+a/C6eMfQyjQN/ZeIT8NOn44YzIMQNo9OzhY+
         exKJ5WHmAqFqRPDws/rq2woXAqgdwLMVNOjNuBW0HtdItY4b9bFKf/4ypriE6SrVk80K
         gETQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to;
        bh=qBfz3tZ1944XpBttA+kX+6/rEWiMdNvuqe4EQMwssok=;
        b=nPqUFPsGQ1xfxDfm1T0ci/oKs5EHFsuYD8EqAs1JivvuEda8V2L2p3Lh8BLVIlsU5/
         WInUb7SvzeSddY3WYt6JAp5y/gAJFJCWpCznWU9/gFgIc9FVmPsN2ffTHBLdu9JUi+d/
         0GhvhCUq07YhlVA4AuJo2xRnas+oPpvTKdfePNfNb9c0IzRuhmNZtTlbqZNQG2viy4Hh
         XxGmPV0qr1BvbWhQdQDuj7pPJNPeCvDiHfmscjW3Mxzvn5UInTBVuytiEHVkS0Z8YEYR
         8a8OQ1MPTrwK7W469+oihdmw1AdCLSoJ1Qf4VtmOP3aghUpTGuArMe5mX+5aBJlr7anC
         4eWw==
X-Gm-Message-State: AN3rC/7v/QSRJ8kDSGoiuM0qY8Hg8jihI+V06DThnoBttB7oG+0WSmK8
	A+06sdCybHcMzofD21BIpUhRcVHcYA==
X-Received: by 10.55.115.67 with SMTP id o64mr1554151qkc.216.1492596643183;
 Wed, 19 Apr 2017 03:10:43 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <od7af6$14nd$1@gioia.aioe.org>
References: <CAA2C=vArYxr2yhJzbjN2c1s3NNzUUEgmY54Qgd4Lsd-29F=uzA AT mail DOT gmail DOT com>
 <od7af6$14nd$1 AT gioia DOT aioe DOT org>
From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Date: Wed, 19 Apr 2017 13:10:42 +0300
Message-ID: <CAA2C=vCdZhQrqLOxehOqx=shUB6Vj9pYprXDNqEbc+jfsY7QKw@mail.gmail.com>
Subject: Re: dxe_tmp.o: linker output file has more than one section
To: djgpp AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 4/19/17, Martin Str|mberg (ams AT ludd DOT luth DOT se) [via
djgpp AT delorie DOT com] <djgpp AT delorie DOT com> wrote:
> "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]"
> <djgpp AT delorie DOT com> wrote:
>> When we try to build a dxe from a C++ project, we hit this error from
>> dxe3gen:
>> dxe_tmp.o: linker output file has more than one section
> ...
>> My question is, has anyone ever hit this error and, if they did, how
>> they overcame it?  Any other advice are also welcome.
>
> No. But dump out the sections from the .o file. Look at the linker
> script in question. I think you'll find the linker script expect one
> section and the .o file have more than one (stating the obvious
> here!).
>
> You need to get rid of the unexpected linker sections. (My first try
> would be to rewrite this part in C.)

Thanks for the answer Martin.

Actually we just solved this:  The culprit was an inline method
having four local variables static: changing them to automatic vars
fixed it.