From owner-freebsd-current  Wed Dec 29 16:27: 0 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184])
	by hub.freebsd.org (Postfix) with ESMTP id 49879156F9
	for <current@freebsd.org>; Wed, 29 Dec 1999 16:26:58 -0800 (PST)
	(envelope-from msmith@mass.cdrom.com)
Received: from mass.cdrom.com (localhost [127.0.0.1])
	by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03126;
	Wed, 29 Dec 1999 16:31:35 -0800 (PST)
	(envelope-from msmith@mass.cdrom.com)
Message-Id: <199912300031.QAA03126@mass.cdrom.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Amancio Hasty <hasty@rah.star-gate.com>
Cc: current@freebsd.org
Subject: Re: gcc compiler problem part deux 
In-reply-to: Your message of "Wed, 29 Dec 1999 16:22:28 PST."
             <199912300022.QAA45237@rah.star-gate.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 29 Dec 1999 16:31:34 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


This was discussed weeks ago, and the new behaviour is correct.  You 
should be using 'cc -E' instead.

> 
> Forgot to post about this new feature of /usr/libexec/cpp :
> 1. Test file
> foo.c
> 
>  main() {
>  #ifdef __FreeBSD__
>  printf("hello\n");
>  #endif
>  }
> 
> 1. old freebsd-current
> 
> 2.   gcc -v
>   Using builtin specs.
>   gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
> 
>  /usr/libexec/cpp foo.c
>  # 1 "foo.c"
>  main() {
> 
>  printf("hello\n");
> 
>  }
> 
> /usr/libexec/cpp has __FreeBSD_ defined --- and this is not 
> problem.
> 
> 2. Now a very recent FreeBSD -current
> gcc -v
> Using builtin specs.
> gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
> 
> /usr/libexec/cpp foo.c
>  # 1 "foo.c"
> 
> 
>  main() {
> 
> 
> 
> }
> 
> Voila! the "printf " disappeared.
> 
> This behavior breaks the XFree86 3.9.17 build because the procedure
> to build imake depends on /usr/libexec/cpp defining __FreeBSD__
> 
> I patched locally the imake build so just for FreeBSD it adds a
> -D__FreeBSD__
> 
> I presumed that the latest /usr/libexec/cpp behavior is also going to 
> break other package. Again for me is not a problem because
> after a few hours I managed to circumvent the new /usr/libexec/cpp
> feature.
> 
> -- 
> 
>  Amancio Hasty
>  hasty@rah.star-gate.com
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  msmith@freebsd.org
\\ and he'll hate you for a lifetime.             \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message