Date:	Tue, 26 Jun 2001 08:50:09 +0300 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	"Mark E." <snowball3 AT bigfoot DOT com>
Cc:	djgpp-workers AT delorie DOT com
Subject:	Re: gcc 3.0 released
In-Reply-To:	<3B376547.14699.24583@localhost>
Message-ID:	<Pine.A41.4.05.10106260848150.34080-100000@ieva06.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 25 Jun 2001, Mark E. wrote:

> > That doesn't really answer my question.  Is ignoring these section a
> > clean solution or not?
> 
> Yes it is.
> 

So should I commit related patch?

Andris

Index: dxegen.c
===================================================================
RCS file: /cvs/djgpp/djgpp/src/dxe/dxegen.c,v
retrieving revision 1.5
diff -p -3 -r1.5 dxegen.c
*** dxegen.c    2001/06/09 21:37:10     1.5
--- dxegen.c    2001/06/26 05:42:24
*************** int main(int argc, char **argv)
*** 186,192 ****
           name
           );
  #endif
!     if (sym[i].e_scnum == 0)
      {
        printf("Error: object contains unresolved external symbols
(%s)\n", name);
        errors ++;
--- 186,195 ----
           name
           );
  #endif
!     /* With gcc-3.0 I'm getting .comment section with e_scnum==0. I don't know
!        whether it's correct to skip it though . It seems to be a problem with binutils.
!        Until it's fixed this helps dxegen to ignore problem ...   (AP)  */
!     if (sym[i].e_scnum == 0 && strncmp(sym[i].e.e_name,".comment",8)!=0)
      {
        printf("Error: object contains unresolved external symbols (%s)\n", name);
        errors ++;

- Raw text -