Re: egcs 1.1a on DEC alpha OSF/3.2, problem with include files

Re: egcs 1.1a on DEC alpha OSF/3.2, problem with include files

[Jeffrey A Law]

  In message < orr9xelie0.fsf@tiete.dcc.unicamp.br >you write:
  > kuball  <kuball@zedo.fuedo.de> writes:
  > 
  > > but why is /usr/local/lib/g++-include in the default path?
  > 
  > I guess it is obtained from the local-prefix.
Nope.  It's from old_gxx_include_dir.

Support for old_gxx_include_dir should probably just go away.  The
g++ header files moved a while ago and trying to compile the very
old libg++ releases which use the old location probably doesn't work
anyway.

jeff

Re: egcs 1.1a on DEC alpha OSF/3.2, problem with include files

[Alexandre Oliva]

Jeffrey A Law <law@cygnus.com> writes:

> Support for old_gxx_include_dir should probably just go away.

Or should we just move /usr/local/g++ to somewhere *after* the
standard include path?  Otherwise, it would break installations of
poeple who have installed C++ include-files unrelated to g++ in
/usr/local/g++.

Which would you prefer me to do?

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil

Re: egcs 1.1a on DEC alpha OSF/3.2, problem with include files

[Jeffrey A Law]

  In message < orn281t5mf.fsf@tiete.dcc.unicamp.br >you write:
  > Jeffrey A Law <law@cygnus.com> writes:
  > 
  > > Support for old_gxx_include_dir should probably just go away.
  > 
  > Or should we just move /usr/local/g++ to somewhere *after* the
  > standard include path?  Otherwise, it would break installations of
  > poeple who have installed C++ include-files unrelated to g++ in
  > /usr/local/g++.
  > 
  > Which would you prefer me to do?
I'd prefer to see it go away, but I do understand the risks involved.

Moving it to last in the search path seems like a reasonable
compromise.

jeff

Re: egcs 1.1a on DEC alpha OSF/3.2, problem with include files

[Alexandre Oliva]

[-- Attachment #1: Type: text/plain, Size: 499 bytes --]

Jeffrey A Law <law@cygnus.com> writes:

>   In message < orn281t5mf.fsf@tiete.dcc.unicamp.br >you write:
>> Jeffrey A Law <law@cygnus.com> writes:
>> 
>> > Support for old_gxx_include_dir should probably just go away.

Agreed.  Unless we're going to support include/g++ in addition to
include/g++-2, which I'd prefer that we didn't.

Ok to install?

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil

[-- Attachment #2: cpppath.diff --]
[-- Type: text/x-diff, Size: 2787 bytes --]

for gcc/ChangeLog
	* cpplib.c: removed OLD_GPLUSPLUS_INCLUDE_DIR
	* cccp.c: ditto
	* Makefile.in (old_gxx_include_dir): removed

Index: gcc/cccp.c
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/gcc/cccp.c,v
retrieving revision 1.33
diff -u -r1.33 cccp.c
--- cccp.c	1998/08/26 08:11:09	1.33
+++ cccp.c	1998/09/16 01:06:03
@@ -421,7 +421,6 @@
   = {
     /* Pick up GNU C++ specific include files.  */
     { GPLUSPLUS_INCLUDE_DIR, "G++", 1, 1 },
-    { OLD_GPLUSPLUS_INCLUDE_DIR, 0, 1, 1 },
 #ifdef CROSS_COMPILE
     /* This is the dir for fixincludes.  Put it just before
        the files that we fix.  */
Index: gcc/cpplib.c
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/gcc/cpplib.c,v
retrieving revision 1.30
diff -u -r1.30 cpplib.c
--- cpplib.c	1998/08/26 08:11:15	1.30
+++ cpplib.c	1998/09/16 01:06:05
@@ -297,7 +297,6 @@
   = {
     /* Pick up GNU C++ specific include files.  */
     { GPLUSPLUS_INCLUDE_DIR, "G++", 1, 1 },
-    { OLD_GPLUSPLUS_INCLUDE_DIR, 0, 1, 1 },
 #ifdef CROSS_COMPILE
     /* This is the dir for fixincludes.  Put it just before
        the files that we fix.  */
Index: gcc/Makefile.in
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/gcc/Makefile.in,v
retrieving revision 1.170
diff -u -r1.170 Makefile.in
--- Makefile.in	1998/09/09 11:33:00	1.170
+++ Makefile.in	1998/09/16 01:06:06
@@ -272,10 +272,6 @@
 libsubdir = $(libdir)/gcc-lib/$(target_alias)/$(version)
 # Directory in which the compiler finds g++ includes.
 gxx_include_dir= @gxx_include_dir@
-# Directory in which the old g++ header files may be found.
-# The reason we use $(libdir)/g++-include rather than using libsubdir
-# is for compatibility with older versions of libg++.
-old_gxx_include_dir= $(libdir)/g++-include
 # Directory to search for site-specific includes.
 includedir = $(local_prefix)/include
 # assertdir is overridden in cross-make.
@@ -1864,7 +1860,6 @@
 	$(CC) $(ALL_CFLAGS) $(ALL_CPPFLAGS) $(INCLUDES) \
 	  -DGCC_INCLUDE_DIR=\"$(libsubdir)/include\" \
 	  -DGPLUSPLUS_INCLUDE_DIR=\"$(gxx_include_dir)\" \
-	  -DOLD_GPLUSPLUS_INCLUDE_DIR=\"$(old_gxx_include_dir)\" \
 	  -DLOCAL_INCLUDE_DIR=\"$(includedir)\" \
 	  -DCROSS_INCLUDE_DIR=\"$(tooldir)/sys-include\" \
 	  -DTOOL_INCLUDE_DIR=\"$(tooldir)/include\" \
@@ -1883,7 +1878,6 @@
 	$(CC) $(ALL_CFLAGS) $(ALL_CPPFLAGS) $(INCLUDES) \
 	  -DGCC_INCLUDE_DIR=\"$(libsubdir)/include\" \
 	  -DGPLUSPLUS_INCLUDE_DIR=\"$(gxx_include_dir)\" \
-	  -DOLD_GPLUSPLUS_INCLUDE_DIR=\"$(old_gxx_include_dir)\" \
 	  -DLOCAL_INCLUDE_DIR=\"$(includedir)\" \
 	  -DCROSS_INCLUDE_DIR=\"$(tooldir)/sys-include\" \
 	  -DTOOL_INCLUDE_DIR=\"$(tooldir)/include\" \

Re: egcs 1.1a on DEC alpha OSF/3.2, problem with include files

[Jeffrey A Law]

  In message < ord88wsw5j.fsf@tiete.dcc.unicamp.br >you write:
  > Agreed.  Unless we're going to support include/g++ in addition to
  > include/g++-2, which I'd prefer that we didn't.
  > 
  > Ok to install?
  > 
[ ... ]

  > for gcc/ChangeLog
  > 	* cpplib.c: removed OLD_GPLUSPLUS_INCLUDE_DIR
  > 	* cccp.c: ditto
  > 	* Makefile.in (old_gxx_include_dir): removed
Looks fine to me.

If we later find that this causes problems for some reason, we'll
just have to back it out and put it at the end of the include path.

jeff

Re: egcs 1.1a on DEC alpha OSF/3.2, problem with include files

[kuball]

On 15 Sep , Jeffrey A Law wrote:
> 
> 
>   In message < orn281t5mf.fsf@tiete.dcc.unicamp.br >you write:
>   > Jeffrey A Law <law@cygnus.com> writes:
>   > 
>   > > Support for old_gxx_include_dir should probably just go away.
>   > 
>   > Or should we just move /usr/local/g++ to somewhere *after* the
>   > standard include path?  Otherwise, it would break installations of
>   > poeple who have installed C++ include-files unrelated to g++ in
>   > /usr/local/g++.
>   > 
>   > Which would you prefer me to do?
> I'd prefer to see it go away, but I do understand the risks involved.
> 
> Moving it to last in the search path seems like a reasonable
> compromise.

Why have it in the path at all? When somebody wants to use old stuff he
can use -I<directory> to add the directory to the search path.

Martin Kuball

Annoying bug in g++ current (egcs-2.92.04 19980914) frontend

[Theodore Papadopoulo]

	IMHO, the following code should compile...

template <class T>
class B {
	typedef T Real;
};


template <class Real>
class A : B<Real> {
 	typedef Real type;
};

mururoa->/u/corse/2/robotvis/egcs2.6/bin/g++ test2.C 
test2.C:9: re-using name of template parameter `Real' in this scope
test2.C:7:  previously declared here `class Real'

It works fine with the 1.1 release. Am I wrong to consider this a bug?


	Thank's lot,

	Theo.

--------------------------------------------------------------------
Theodore Papadopoulo
Email: Theodore.Papadopoulo@sophia.inria.fr Tel: (33) 04 92 38 76 01
 --------------------------------------------------------------------

Re: Annoying bug in g++ current (egcs-2.92.04 19980914) frontend

[Martin von Loewis]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

> It works fine with the 1.1 release. Am I wrong to consider this a bug?

Yes. According to 14.6.1, [temp.local]/4, your example is ill-formed:

>> A template­parameter shall not be redeclared within its scope
>> (including nested scopes). A template­parameter shall not have the
>> same name as the template name. [Example: 
>>  template<class T, int i>
>>  class Y { 
>>    int T; // error: template­parameter redeclared 
>>    void f()
>>    { char T; // error: template­parameter redeclared 
>>    } 
>>  };
>>  template<class X> class X; // error: template­parameter redeclared

Egcs 1.1 does not diagnose this rule, and assumes that the local
names hide the template parameters, instead.

Regards,
Martin