public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: hjl@lucon.org (H.J. Lu)
To: haible@ilog.fr (Bruno Haible)
Cc: egcs@cygnus.com, libc-hacker@cygnus.com (GNU C Library),
	linux-gcc@vger.rutgers.edu (linuxgcc)
Subject: libg++ 2.8.1 980505 is available.
Date: Wed, 06 May 1998 09:19:00 -0000	[thread overview]
Message-ID: <m0yWvKN-000268C@ocean.lucon.org> (raw)
In-Reply-To: <199805051245.OAA02810@halles.ilog.fr>

> 
> H.J., you can now drop gperf from libg++.
> 

Done.

-- 
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 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.2 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.1-980505.tar.gz
ftp://ftp.kernel.org/pub/linux/devel/gcc/libg++-2.8.1-980505.tar.gz

Patch for libg++ 2.8.1 980415 is also available at

ftp://ftp.yggdrasil.com/private/hjl/libg++-2.8.1-980415-980505.diff.gz
ftp://ftp.kernel.org/pub/linux/devel/gcc/libg++-2.8.1-980415-980505.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.1-980415-tar.gz | tar xf -

Or

# cd src/libstdc++-2.8.1
# gzip -dc xxxxxx/libg++-2.8.1-980415-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
05/05/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

      reply	other threads:[~1998-05-06  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-05  5:46 gperf-2.7 is released Bruno Haible
1998-05-06  9:19 ` H.J. Lu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m0yWvKN-000268C@ocean.lucon.org \
    --to=hjl@lucon.org \
    --cc=egcs@cygnus.com \
    --cc=haible@ilog.fr \
    --cc=libc-hacker@cygnus.com \
    --cc=linux-gcc@vger.rutgers.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).