buildworld failure in libstdc++

2002-07-16 Thread Michael Reifenberger

Hi,
a make depend in /usr/src/gnu/lib/libstdc++ breaks with:
...
/usr/include/g++/backward/backward_warning.h:32:2: warning: #warning This file
includes at least one deprecated or antiquated header. Please consider using one
of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples
include substituting the X header for the X.h header for C++ includes, or
sstream instead of the deprecated header strstream.h. To disable this
warning use -Wno-deprecated.
In file included from /usr/src/contrib/libstdc++/libsupc++/eh_alloc.cc:37:
/usr/src/contrib/libstdc++/libsupc++/unwind-cxx.h:41:20: unwind.h: No such file
or directory
In file included from /usr/src/contrib/libstdc++/libsupc++/eh_aux_runtime.cc:34:



Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: buildworld failure in libstdc++

2002-07-16 Thread Michael Reifenberger

On Tue, 16 Jul 2002, Michael Reifenberger wrote:
...
 /usr/include/g++/backward/backward_warning.h:32:2: warning: #warning This file
 includes at least one deprecated or antiquated header. Please consider using one
 of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples
 include substituting the X header for the X.h header for C++ includes, or
 sstream instead of the deprecated header strstream.h. To disable this
 warning use -Wno-deprecated.
 In file included from /usr/src/contrib/libstdc++/libsupc++/eh_alloc.cc:37:
 /usr/src/contrib/libstdc++/libsupc++/unwind-cxx.h:41:20: unwind.h: No such file
 or directory
 In file included from /usr/src/contrib/libstdc++/libsupc++/eh_aux_runtime.cc:34:

Just after writing I started thinking :-(
I was missing the + in /etc/make.conf's CFLAGS += ... and CXXFLAGS += ...
Sorry for the false alarm.

Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: buildworld failure in libstdc++

2002-07-16 Thread Steve Kargl

On Tue, Jul 16, 2002 at 11:54:02AM +0200, Michael Reifenberger wrote:
 On Tue, 16 Jul 2002, Michael Reifenberger wrote:
 ...
  /usr/include/g++/backward/backward_warning.h:32:2: warning: #warning This file
  includes at least one deprecated or antiquated header. Please consider using one
  of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples
  include substituting the X header for the X.h header for C++ includes, or
  sstream instead of the deprecated header strstream.h. To disable this
  warning use -Wno-deprecated.
  In file included from /usr/src/contrib/libstdc++/libsupc++/eh_alloc.cc:37:
  /usr/src/contrib/libstdc++/libsupc++/unwind-cxx.h:41:20: unwind.h: No such file
  or directory
  In file included from /usr/src/contrib/libstdc++/libsupc++/eh_aux_runtime.cc:34:
 
 Just after writing I started thinking :-(
 I was missing the + in /etc/make.conf's CFLAGS += ... and CXXFLAGS += ...
 Sorry for the false alarm.
 

You don't need a + in CFLAGS in /etc/make.conf.  You need a +=
in CXXFLAGS if you want CXXFLAGS to contain the contents of CFLAGS.
See /usr/share/examples/etc/make.conf.


-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: buildworld failure in libstdc++

2002-07-16 Thread Michael Reifenberger

On Tue, 16 Jul 2002, Steve Kargl wrote:

 Date: Tue, 16 Jul 2002 07:30:01 -0700
 From: Steve Kargl [EMAIL PROTECTED]
 To: Michael Reifenberger [EMAIL PROTECTED]
 Cc: FreeBSD-Current [EMAIL PROTECTED]
 Subject: Re: buildworld failure in libstdc++

...
 You don't need a + in CFLAGS in /etc/make.conf.  You need a +=
 in CXXFLAGS if you want CXXFLAGS to contain the contents of CFLAGS.
 See /usr/share/examples/etc/make.conf.
Ah, I see.
Thanks!

BTW: I need NO_WARNS=YES to get /usr/src/libexec/rtld-elf compiled.

Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: buildworld failure in libstdc++

2002-07-16 Thread Michael Reifenberger

On Tue, 16 Jul 2002, Steve Kargl wrote:
...
 Is this an alpha based system?  I just completed a buildworld
 without setting anything special.
i386
Sigh.
It must have been a relict of using the ports gcc31 for buildworld.
Another make (using the base 3.1 compiler - in /usr/src/libexec/rtld-elf after
make installworld succeeded too.

Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: buildworld failure in libstdc++

2002-07-16 Thread Rob Hughes

On Tue, 2002-07-16 at 17:11, Michael Reifenberger wrote:
 On Tue, 16 Jul 2002, Steve Kargl wrote:
 ...
  Is this an alpha based system?  I just completed a buildworld
  without setting anything special.
 i386
 Sigh.
 It must have been a relict of using the ports gcc31 for buildworld.
 Another make (using the base 3.1 compiler - in /usr/src/libexec/rtld-elf after
 make installworld succeeded too.
 

Broken here, using a nothing from ports, base system only.

-- 
Remember: the only difference between
being the champ and the chump is u.



signature.asc
Description: This is a digitally signed message part