Re: ident problems using gnu tools

• Date: Fri, 4 Oct 1996 12:07:09 PDT
• From:
  "Marty Leisner" <leisner@sdsp.mc.xerox.com>
• Reply-To:
  "Marty Leisner" <leisner@sdsp.mc.xerox.com>
• Cc: crossgcc@cygnus.com
• In-Reply-To: Your message of "Fri, 04 Oct 1996 09:55:36 PDT." <199610041655.MAA15297@jupiter.curtech.com>

In message <199610041655.MAA15297@jupiter.curtech.com>,   you write:
>
>I seem to be having problems when trying to find what makes up an executable
>using the "what" command. It looks like the gnu assembler and linker don't 
>keep the .ident portion in the executable.
>
>This is using gcc-2.7.2.1 and binutils 2.5.2. I have tried this as a native
>on Sunos4.1.3 and as a cross to m68k-coff, both strip out ident messages.
>
>It seems to work if I use the native linker and assembler, but I would really
>like to use the GNU binutils, and in the case of cross-development need to
>use them. Are there any tricks to get as and ld to keep the .ident strings


Is an ident string from the
#ident 
non-ansi nonsense?

just put in your source files:

static char rcsid[] = "$Id$"

or

static char sccsid[] = "%W% %G% %U%"

or whathaveyou for your source ontrol.

marty

• Re: ident problems using gnu tools
• From: "Robert J. Brown" <rj@eli.wariat.org>
• Re: ident problems using gnu tools
• From: Stephen Williams <steve@icarus.com>

• ident problems using gnu tools
• From: Rich Casselberry <richc@curtech.com>

• Prev: ident problems using gnu tools
• Next: Re: ident problems using gnu tools
• Index: Cross gcc Mailing list
• Thread: Cross gcc Mailing list