public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Where is std.h ?
@ 1998-07-07 16:57 Alex Lam
  1998-07-08  9:58 ` Joe Buck
  1998-07-08 13:00 ` libg++ 2.8.2 980708 addon is released H.J. Lu
  0 siblings, 2 replies; 4+ messages in thread
From: Alex Lam @ 1998-07-07 16:57 UTC (permalink / raw)
  To: egcs, egcs-bugs

Hi, 

I was trying to compile a c++ program on RedHat 5.1 and I discovered
that there is no std.h in egcs-1.0.2.

I don't think it's in 1.0.3a either, has it been obsoleted ?

Thanks.

Alex




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

* Re: Where is std.h ?
  1998-07-07 16:57 Where is std.h ? Alex Lam
@ 1998-07-08  9:58 ` Joe Buck
  1998-07-08 13:00 ` libg++ 2.8.2 980708 addon is released H.J. Lu
  1 sibling, 0 replies; 4+ messages in thread
From: Joe Buck @ 1998-07-08  9:58 UTC (permalink / raw)
  To: Alex Lam; +Cc: egcs, egcs-bugs

> I was trying to compile a c++ program on RedHat 5.1 and I discovered
> that there is no std.h in egcs-1.0.2.

No, std.h was a libg++ thing, and should have been dumped a long time ago,
since it just duplicates standard C headers.  It was originally around
because it goes back to the days when most people didn't have standard
ANSI C headers on their systems.

> I don't think it's in 1.0.3a either, has it been obsoleted ?

Yes, use <stdlib.h> and/or <string.h> .



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

* libg++ 2.8.2 980708 addon is released.
  1998-07-07 16:57 Where is std.h ? Alex Lam
  1998-07-08  9:58 ` Joe Buck
@ 1998-07-08 13:00 ` H.J. Lu
  1998-07-08 18:52   ` Joe Buck
  1 sibling, 1 reply; 4+ messages in thread
From: H.J. Lu @ 1998-07-08 13:00 UTC (permalink / raw)
  To: Alex Lam; +Cc: egcs

> 
> Hi, 
> 
> I was trying to compile a c++ program on RedHat 5.1 and I discovered
> that there is no std.h in egcs-1.0.2.
> 

<std.h> is in libg++.

This is my new libg++ addon for egcs and libstdc++. It is strongly
recommended to install it if you work on egcs and compile the C++
compiler. It is a very good testbed for C++ and egcs in general.

Thanks.


-- 
H.J. Lu (hjl@gnu.org)
----
This is a libg++ addon for libstdc++ 2.8.1 and egcs. It is needed only
if your applications depend on libg++ and the dependency on libg++
cannot be removed easily. The standalone libg++ is not longer needed.

Changes from libg++ 2.8.1 980505:

1. Add the interface support for the library names.
2. Handle --enable-version-specific-runtime-libs.
3. Fix a parallel build bug.
4. A librx bug fix.

Changes from libg++ 2.8.1 980415:

1. gperf is removed from libg++. The stand-alone gperf is available at

ftp://ftp.gnu.org/pub/gnu/

The current version, as of May 5, 1998, is gperf 2.7.

The libg++ and librx have been tested with

1. egcs 1.0.3 on linux/x86/libc 5, linux/x86/glibc 2.1 and
   linux/alpha/glibc 2.0.7.
2. gcc 2.8.1 980209 and libstdc++ 2.8.1 980228 on linux/x86/libc 5.

It is available at

ftp://ftp.yggdrasil.com/private/hjl/libg++-2.8.2-980708.tar.gz
ftp://ftp.kernel.org/pub/linux/devel/gcc/libg++-2.8.2-980708.tar.gz

Patch for libg++ 2.8.1 980505 is also available at

ftp://ftp.yggdrasil.com/private/hjl/libg++-2.8.2-980505-980708.diff.gz
ftp://ftp.kernel.org/pub/linux/devel/gcc/libg++-2.8.2-980505-980708.diff.gz

Just put libg++ and librx under the egcs or libstdc++ source directory,
i.e.,

# cd src/egcs
# gzip -dc xxxxxx/libg++-2.8.2-980708-tar.gz | tar xf -

Or

# cd src/libstdc++-2.8.1
# gzip -dc xxxxxx/libg++-2.8.2-980708-tar.gz | tar xf -

Potential problems with libstdc++ 2.8.1:

1. Since gcc 2.8.1 is installed under /usr on Linux/GNU, libstdc++
   should be modified to reflect it. Otherwise incorrect header files
   and libraries may be used. A patch is available upon request.

You also need to check configure.in and configure to see if the
patch enclosed here is already applied. If not, please do

# patch -p0 < README.libg++

Then you can configure/build/check/install egcs normally. Now it
will include libg++.


H.J. Lu
hjl@gnu.org
07/08/1998
--- 
Sun Sep  7 14:27:56 1997  H.J. Lu  (hjl@gnu.ai.mit.edu)

	* configure.in (alpha*-*-linux*): Treat alpha*-*-linux* as
	alpha*-*-linux* and alpha*-*-*.

Mon Aug 25 17:31:49 1997  H.J. Lu  (hjl@gnu.ai.mit.edu)

	* configure: When making link, also check the current
	directory. The configure scripts may create one.

Index: configure.in
===================================================================
RCS file: /home/work/cvs/gnu/egcs/configure.in,v
retrieving revision 1.1.1.4
diff -u -r1.1.1.4 configure.in
--- configure.in	1997/09/17 20:09:19	1.1.1.4
+++ configure.in	1997/10/23 00:01:53
@@ -416,6 +507,12 @@
   alpha*-*-*vms*)
     noconfigdirs="$noconfigdirs gdb ld target-newlib target-libgloss"
     ;;
+  alpha*-*-linux*)
+    # newlib is not 64 bit ready
+    noconfigdirs="$noconfigdirs target-newlib target-libgloss"
+    # linux has rx in libc
+    skipdirs="$skipdirs target-librx"
+    ;;
   alpha*-*-*)
     # newlib is not 64 bit ready
     noconfigdirs="$noconfigdirs target-newlib target-libgloss"
Index: configure
===================================================================
RCS file: /home/work/cvs/gnu/egcs/configure,v
retrieving revision 1.1.1.2
diff -u -r1.1.1.2 configure
--- configure	1997/09/17 20:09:18	1.1.1.2
+++ configure	1997/09/17 20:22:21
@@ -992,27 +1006,34 @@
                 set ${links}; link=$1; shift; links=$*
 
                 if [ ! -r ${srcdir}/${file} ] ; then
+                  if [ ! -r ${file} ] ; then
+		    
                         echo '***' "${progname}: cannot create a link \"${link}\"," 1>&2
                         echo '***' "since the file \"${srcdir}/${file}\" does not exist." 1>&2
                         exit 1
+		  else
+			srcfile=${file}
+		  fi
+		else
+			srcfile=${srcdir}/${file}
                 fi
 
                 ${remove} -f ${link}
 		# Make a symlink if possible, otherwise try a hard link
-		if ${symbolic_link} ${srcdir}/${file} ${link} >/dev/null 2>&1 ; then
+		if ${symbolic_link} ${srcfile} ${link} >/dev/null 2>&1 ; then
 			true
 		else
 			# We need to re-remove the file because Lynx leaves a 
 			# very strange directory there when it fails an NFS symlink.
 			${remove} -r -f ${link}
-			${hard_link} ${srcdir}/${file} ${link}
+			${hard_link} ${srcfile} ${link}
 		fi
                 if [ ! -r ${link} ] ; then
-                        echo '***' "${progname}: unable to link \"${link}\" to \"${srcdir}/${file}\"." 1>&2
+                        echo '***' "${progname}: unable to link \"${link}\" to \"${srcfile}\"." 1>&2
                         exit 1
                 fi
 
-                echo "Linked \"${link}\" to \"${srcdir}/${file}\"."
+                echo "Linked \"${link}\" to \"${srcfile}\"."
         done
 
         # Create a .gdbinit file which runs the one in srcdir

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

* Re: libg++ 2.8.2 980708 addon is released.
  1998-07-08 13:00 ` libg++ 2.8.2 980708 addon is released H.J. Lu
@ 1998-07-08 18:52   ` Joe Buck
  0 siblings, 0 replies; 4+ messages in thread
From: Joe Buck @ 1998-07-08 18:52 UTC (permalink / raw)
  To: H.J. Lu; +Cc: alexl, egcs

> > I was trying to compile a c++ program on RedHat 5.1 and I discovered
> > that there is no std.h in egcs-1.0.2.
> > 
> 
> <std.h> is in libg++.
> 
> This is my new libg++ addon for egcs and libstdc++. It is strongly
> recommended to install it if you work on egcs and compile the C++
> compiler. It is a very good testbed for C++ and egcs in general.

While libg++ is nice for testing (because the libstdc++ testsuite is so
weak), I'd recommend against using std.h.  Its use means that you've
written a less portable program (it requires both g++ and libg++).



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

end of thread, other threads:[~1998-07-08 18:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-07-07 16:57 Where is std.h ? Alex Lam
1998-07-08  9:58 ` Joe Buck
1998-07-08 13:00 ` libg++ 2.8.2 980708 addon is released H.J. Lu
1998-07-08 18:52   ` Joe Buck

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