Article View: gnu.gcc.help
Article #51753gcc 2.3.3 & gas 2.0 config problem
From: Daniel W. Muller
Date: Fri, 09 Apr 1993 14:55
Date: Fri, 09 Apr 1993 14:55
52 lines
2832 bytes
2832 bytes
I need help with a problem which I encountered while trying to build gcc 2.3.3 with the following configuration: --with-gnu-as --with-gnu-ld --with-minimal-bfd i386-sysv32 (I also used a --prefix option which I left out of the above.) This configuration was used for all of the build directories mentioned below. I had to modify the configure.in script slightly for gas 2.0 - it looked for a ho-sysv32.h file, which doesn't exist. I changed the script so that *-*-sysv* gets the ho-sysv.h file. Then I build the gcc target start.encap. No problem. Then I build binutils 2.1. No problem. Then I build ld 2.1 (with BFD 2.1). No problem. Then I build rest.encap. Here's where I run into a problem. While trying to compile enquire.c, the following errors occur: crtstuff.s:7: Warning: unknown section attribute 'a' crtstuff.s:7: Rest of line ignored. First ignored character is `,'. crtstuff.s:14: Warning: unknown section attribute 'a' crtstuff.s:14: Rest of line ignored. First ignored character is `,'. gmake: *** [crtbegin.o] Error 1 Apparently, the configuration combination i386-sysv and --with-gas causes gcc to be built such that it uses the "default" assembler op for starting the initialization code section, defined in crtstuff.c as: section .ctors,"a",@progbits However, gas only recognizes the section attribute letters bilnowx. (Cf. function obj_coff_section in obj-coffbfd.h.) Unfortunately, I'm not familiar with UNIX assembler details, so I don't know what these various letters mean. (That's one of the things I love about UNIX... I never had to know this stuff before!) Without the --with-gas configuration option, the following assembler op, defined in svr3.h, would have been used by gcc: section .ctors,"x" I think I need to use --with-gas in order to get decent C++ debugging with gdb in my environment, which is derived from SysV3.2. Is this correct? If so, how do I resolve this mismatch between gcc and gas? Thanks in advance for any help, -- Dan Muller [ "So that's what an invisible barrier ] Banyan Systems Inc. [ looks like!" (the movie: Time Bandits) ]
Technical Details
Message-ID:
<930409095554@helvetica.banyan.com>Path:
arc1-ca.pugleaf.net!gmd.de!ira.uka.de!sol.ctr.columbia.edu!howland.reston.ans.net!noc.near.net!squam.banyan.com!helvetica.banyan.com!danmShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,51328b2d623e0d7a,start X-Google-Attributes: gid11318c,public X-Google-ArrivalTime: 1993-04-09 07:09:05 PST Newsgroups: gnu.gcc.help Path: arc1-ca.pugleaf.net!gmd.de!ira.uka.de!sol.ctr.columbia.edu!howland.reston.ans.net!noc.near.net!squam.banyan.com!helvetica.banyan.com!danm From: danm@squam.banyan.com (Daniel W. Muller) Subject: gcc 2.3.3 & gas 2.0 config problem Message-ID: <930409095554@helvetica.banyan.com> Nntp-Software: PC/TCP NNTP Lines: 52 Sender: usenet@squam.banyan.com (Usenet ID) Reply-To: danm@banyan.com Organization: Banyan Systems, Inc. Date: Fri, 9 Apr 1993 14:55:54 GMT