public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: libstdc++/3353: Problem while generating .h file...
@ 2001-06-21 20:30 ljrittle
  0 siblings, 0 replies; 2+ messages in thread
From: ljrittle @ 2001-06-21 20:30 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, jma, ljrittle, nobody

Synopsis: Problem while generating .h file...

Responsible-Changed-From-To: unassigned->ljrittle
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Thu Jun 21 20:30:30 2001
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: open->closed
State-Changed-By: ljrittle
State-Changed-When: Thu Jun 21 20:30:30 2001
State-Changed-Why:
    Duplicate of 3 other reports (Mandrake 8.0 users trying to
    bootstrap gcc 3.0, I am sorry!)

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3353&database=gcc


^ permalink raw reply	[flat|nested] 2+ messages in thread

* libstdc++/3353: Problem while generating .h file...
@ 2001-06-21 19:16 jma
  0 siblings, 0 replies; 2+ messages in thread
From: jma @ 2001-06-21 19:16 UTC (permalink / raw)
  To: gcc-gnats

>Number:         3353
>Category:       libstdc++
>Synopsis:       Problem while generating .h file...
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 21 19:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     jma@netgem.com
>Release:        gcc 3.0
>Organization:
>Environment:
Linux Mandrake 8.0
Kernel 2.4.3 with gcc 2.96 from Mandrake...
>Description:
I had a problem while generating gthr.h file.
In fact, there is a preprocessing file using sed
which change every #something into #_GLIBCPP_something
in this file.
So, the sources which include this file cannot compile any more,
as the preprocessor gets, for example:
#__GLICPP_ifdef something ....

So, I removed the sed preprocessing of this file and everything seems 
to be all right. I modified acinclude.m4 and aclocal.m4.

I feel that it's not the real correct patch to apply,
but I don't know what was the real goal of the preprocessing
that was to be done...

I use gcc 3.0 since it cames out.
Seems really all right !!!

Regards.

Jocelyn Mayer.
>How-To-Repeat:
I compiled gcc 3.0 using:

../gcc-3.0/configure --prefix=/usr --host=i686-pc-linux-gnu --enable-shared 
>Fix:
--- acinclude.m4-orig	Fri Jun 22 03:51:59 2001
+++ acinclude.m4	Fri Jun 22 03:51:45 2001
@@ -1155,7 +1155,8 @@
   fi
   AC_OUTPUT_COMMANDS([d=include/bits
     rm -f $d/gthr.h $d/gthr-single.h $d/gthr-default.h
-    sed '/^#/s/\([A-Z_][A-Z_]*\)/_GLIBCPP_\1/g' <$d/gthr.h-in >$d/gthr.h
+#    sed '/^#/s/\([A-Z_][A-Z_]*\)/_GLIBCPP_\1/g' <$d/gthr.h-in >$d/gthr.h
+    cp gthr.h-in $d/gthr.h
     sed 's/\(UNUSED\)/_GLIBCPP_\1/g' <$d/gthr-single.h-in \
       | sed 's/\(GCC[A-Z_]*_H\)/_GLIBCPP_\1/g' >$d/gthr-single.h
     sed 's/\(UNUSED\)/_GLIBCPP_\1/g' <$d/gthr-default.h-in \


--- aclocal.m4-orig	Fri Jun 22 03:53:27 2001
+++ aclocal.m4	Fri Jun 22 03:53:17 2001
@@ -1167,7 +1167,8 @@
   fi
   AC_OUTPUT_COMMANDS([d=include/bits
     rm -f $d/gthr.h $d/gthr-single.h $d/gthr-default.h
-    sed '/^#/s/\([A-Z_][A-Z_]*\)/_GLIBCPP_\1/g' <$d/gthr.h-in >$d/gthr.h
+#    sed '/^#/s/\([A-Z_][A-Z_]*\)/_GLIBCPP_\1/g' <$d/gthr.h-in >$d/gthr.h
+    cp $d/gthr.h-in $d/gthr.h
     sed 's/\(UNUSED\)/_GLIBCPP_\1/g' <$d/gthr-single.h-in \
       | sed 's/\(GCC[A-Z_]*_H\)/_GLIBCPP_\1/g' >$d/gthr-single.h
     sed 's/\(UNUSED\)/_GLIBCPP_\1/g' <$d/gthr-default.h-in \
>Release-Note:
>Audit-Trail:
>Unformatted:


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-06-21 20:30 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-06-21 20:30 libstdc++/3353: Problem while generating .h file ljrittle
  -- strict thread matches above, loose matches on Subject: below --
2001-06-21 19:16 jma

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).