On Thu, Oct 02, 2003 at 02:31:38PM +1000, Kevin Saenz wrote:
> Aren't they part of the .h files?
Yes, but the compiler also defines some - some are internal (compiled
into gcc when it was built), some are based on command line switches
(try adding -march=i686 and see what changes) and others are
gcc -v show up wht is passed into cpp for my RH8.0 box, I can see all the
standard ones..
Dave.
On Thu, 2 Oct 2003, Tiwari, Rajnish wrote:
> Hi All,
>
> How can I quickly find out what internal #defines are
> set by gcc during compile ?
>
> Thanks in advance.
>
> Regards,
> Ra
Tiwari, Rajnish wrote:
How can I quickly find out what internal #defines are
set by gcc during compile ?
$ gcc -dM -E -
--
Chris Johns, cjohns at cybertec . com . au
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
On Thu, Oct 02, 2003 at 02:24:44PM +1000, Tiwari, Rajnish wrote:
> How can I quickly find out what internal #defines are
> set by gcc during compile ?
[EMAIL PROTECTED] ~]$ touch tmp.c
[EMAIL PROTECTED] ~]$ gcc -E -dM tmp.c
#define __USER_LABEL_PREFIX__
#define __SIZE_
Aren't they part of the .h files?
> Hi All,
>
> How can I quickly find out what internal #defines are
> set by gcc during compile ?
>
> Thanks in advance.
>
> Regards,
> Rajnish
--
Regards,
Kevin Saenz
Spinaweb
I.T consultants
Ph: 02 4620 5130
Fax: 02 4625 9243
Mobile: 0
Hi All,
How can I quickly find out what internal #defines are
set by gcc during compile ?
Thanks in advance.
Regards,
Rajnish
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
