From: Barry Clarkson <cheekyscamp@yahoo.co.uk>
To: gcc-help@gcc.gnu.org
Subject: #ident query
Date: Wed, 22 Dec 2004 07:39:00 -0000 [thread overview]
Message-ID: <20041222073856.19981.qmail@web90106.mail.scd.yahoo.com> (raw)
Hi,
I'm in the process of porting some code to a Linux
based platform that is using gcc 3.2.2. I am trying
to enforce ansi C (as near as possible!) but there are
#ident directives within the code for third party
source control. What can I modify within the source
(not ideal) or on the command line to get ansi C and
safely ignore the '#ident' directives (tried
-fno-ident)?
Thanks in advance,
Barry
GCC version...
$ gcc -v
Reading specs from
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs
Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--enable-shared --enable-threads=posix
--disable-checking --with-system-zlib
--enable-__cxa_atexit --host=i386-redhat-linux
Thread model: posix
gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
Command line...
gcc -c -g -ansi -std=c99 -pedantic-errors -Wall
-Wundef -Wshadow -Wunreachable-code -Wno-long-long
-Werror -fno-ident -I../inc -I../proto aps_log_err.c
-o ../obj/aps_log_err.o
aps_log_err.c:31:2: #ident is a GCC extension
Example #ident...
#ident "@(#) SCCS aps_log_err.c 1.7 - 04/10/13
14:02:54"
___________________________________________________________
ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
next reply other threads:[~2004-12-22 7:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 7:39 Barry Clarkson [this message]
2004-12-22 8:02 ` Ken Foskey
2004-12-22 12:32 ` Eljay Love-Jensen
2004-12-22 15:50 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2004-12-20 11:03 Barry Clarkson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041222073856.19981.qmail@web90106.mail.scd.yahoo.com \
--to=cheekyscamp@yahoo.co.uk \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).