linux-gcc-digest Tuesday, 7 September 1999 Volume 01 : Number 398
In this issue:
Re: gdb 4.17.0.13 is released.
Re: gdb 4.17.0.13 is released.
makedepend warning
arrays that are too big
Prblem compiling C++ with G++
glibc 2.1.2pre3
Re: glibc 2.1.2pre3
SPAM
Re: glibc 2.1.2pre3
Re: glibc 2.1.2pre3
Re: glibc 2.1.2pre3
Re: glibc 2.1.2pre3
Re: glibc 2.1.2pre3
Re: SPAM
Re: glibc 2.1.2pre3
Re: arrays that are too big
Re: Prblem compiling C++ with G++
Re: arrays that are too big
Re: arrays that are too big
Re: arrays that are too big
Re: arrays that are too big
binutils 2.9.5.0.10 is released.
glibc 2.1.2
binutils 2.9.5.0.11 is released.
Re: glibc 2.1.2
Re: glibc 2.1.2
Re: glibc 2.1.2
Re: glibc 2.1.2
glibc/binutils upgrade -> g++ reports itself as crosscompiler
Re: glibc 2.1.2
Re: glibc 2.1.2
See the end of the digest for information on subscribing to the linux-gcc
or linux-gcc-digest mailing lists.
----------------------------------------------------------------------
From: [EMAIL PROTECTED] (H.J. Lu)
Date: Mon, 23 Aug 1999 08:08:59 -0700 (PDT)
Subject: Re: gdb 4.17.0.13 is released.
>
> HJ Lu writes:
>
> > This is the beta release of gdb 4.17.0.13, which is based on gdb 4.17
> > plus Linux/x86 hardware watchpoint/FPU, glibc 2 pthread and Linux/PPC
> > support.
>
> Given that 4.18 is the current gdb release, why are you releasing a
> fork off of the old version?
>
>
Have you tried gdb 4.18 on Linux? It lacks many important features
added/fixed in gdb 4.17.0.x. People have been working on it. But it
may not be there until 4.19. So for the time being, Linux has to use
gdb 4.17.0.x if you want to debug thread, FPU and reliable hardware
watchpoint on x86.
BTW, I am working a patch for AMD new chip. I will make 4.17.0.14 after
I get confirmation.
- --
H.J. Lu ([EMAIL PROTECTED])
------------------------------
From: Joe Buck <[EMAIL PROTECTED]>
Date: Mon, 23 Aug 99 8:26:19 PDT
Subject: Re: gdb 4.17.0.13 is released.
I wrote:
> > Given that 4.18 is the current gdb release, why are you releasing a
> > fork off of the old version?
HJ writes:
> Have you tried gdb 4.18 on Linux? It lacks many important features
> added/fixed in gdb 4.17.0.x.
Just the same, gdb 4.18 has a number of bug fixes and other improvements.
Unless you plan to create a permanent fork, life will be easier if you
manage to create patches off of 4.18 (including some of your 4.17.0.x
features not included in 4.18); this will, I think, make it easier for the
gdb team to eventually include your changes.
I notice that you didn't include the gdb maintainance address on your
announcement. Was that an accident?
------------------------------
From: "Godfree" <[EMAIL PROTECTED]>
Date: Wed, 25 Aug 1999 12:40:03 GMT2
Subject: makedepend warning
I get the following error when I run makedepend
makedepend:warning: FindNtrsc.c: 13: #error architecture not
supported by the Linux C library.
I'm not sure waht this error message means. Can someone please help
out.
Regards
Godfree Gert
Department of Medical Physics
University of the Orange Free State
P O Box 339
Bloemfontein
9301
Tel: +27 51 4053158
------------------------------
From: Berkeley Hynes <[EMAIL PROTECTED]>
Date: Wed, 25 Aug 1999 12:26:43 -0400
Subject: arrays that are too big
What is the standard behaviour of a compiled C program which declares an
array which is too big given the system's available memory?
Whenever I use dynamic memeory I always test for malloc's error codes,
but it occurred to me that I don't test anything to make sure an array
has been properly allocated. Should I be testing something?
Thanks in advance,
Berkeley Hynes
[EMAIL PROTECTED]
------------------------------
From: "Andres Tarallo" <[EMAIL PROTECTED]>
Date: Wed, 25 Aug 1999 15:27:22 -0600
Subject: Prblem compiling C++ with G++
I've developed a small class in C++; while compiling it I'm getting
the following message
"return type specification for constructor invalid".
I don't understand this message, what does it mean?. As far as I'm
concerned the constructor does not return anything.
Thanks in advance
Andres Tarallo
------------------------------
From: Ulrich Drepper <[EMAIL PROTECTED]>
Date: 25 Aug 1999 15:06:56 -0700
Subject: glibc 2.1.2pre3
I've uploaded the third prerelease for glibc 2.1.2 to
ftp://sourceware.cygnus.com/pub/glibc
and
ftp://ftp.XX.kernel.org/pub/software/libs/glibc
(where XX is your country code). It soon will also be available on
ftp://alpha.gnu.org/gnu/libc
There you will find the files
glibc-2.1.2pre3.tar.gz
glibc-linuxthreads-2.1.2pre3.tar.gz
and possibly .bz2 versions. There is no new crypt add-on, still use
the version released with glibc 2.1.
Since 2.1.2pre2 we've added lots of changes, especially a number of
patches went in which correct problems with threads. If no problems
are reported I'll make a final 2.1.2 release soon.
So, now is your chance to avoid releasing a buggy version. The
feedback I got for the last prereleases was lousy at best. It might
even be that this version does not even compile on some platforms.
I only have easy access to an x86 and Arm machine (well, there is the
HP but HPPA/Linux does not yet work). So you have to do the tests for
other platforms yourself or put one of the machines you care about
under my desk.
So, test this version and send feedback to [EMAIL PROTECTED]
- --
- ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: Internet Business <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 1999 01:05:05 +0200
Subject: Re: glibc 2.1.2pre3
Ulrich Drepper ha escrito:
> I've uploaded the third prerelease for glibc 2.1.2 to
>
> ftp://sourceware.cygnus.com/pub/glibc
> and
> ftp://ftp.XX.kernel.org/pub/software/libs/glibc
>
> (where XX is your country code). It soon will also be available on
>
> ftp://alpha.gnu.org/gnu/libc
>
> There you will find the files
>
> glibc-2.1.2pre3.tar.gz
> glibc-linuxthreads-2.1.2pre3.tar.gz
>
> and possibly .bz2 versions. There is no new crypt add-on, still use
> the version released with glibc 2.1.
>
> Since 2.1.2pre2 we've added lots of changes, especially a number of
> patches went in which correct problems with threads. If no problems
> are reported I'll make a final 2.1.2 release soon.
>
> So, now is your chance to avoid releasing a buggy version. The
> feedback I got for the last prereleases was lousy at best. It might
> even be that this version does not even compile on some platforms.
>
> I only have easy access to an x86 and Arm machine (well, there is the
> HP but HPPA/Linux does not yet work). So you have to do the tests for
> other platforms yourself or put one of the machines you care about
> under my desk.
>
> So, test this version and send feedback to [EMAIL PROTECTED]
>
> --
> ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: Internet Business <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 1999 01:10:21 +0200
Subject: SPAM
Este es un mensaje de varias partes en formato MIME.
- --------------19854CD2442E19228C3F57D4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Return-path:
<[EMAIL PROTECTED]>
Received:
from hospedando.com (unverified [209.239.32.10]) by
mailsvr2.telebot.net (Rockliffe SMTPRA
3.4.2) with ESMTP id <[EMAIL PROTECTED]>
for <[EMAIL PROTECTED]>; Wed, 25
Aug 1999 15:52:19 -0700
Received:
(from ipic@localhost) by hospedando.com (8.9.3/8.9.3)
id SAA11148 for [EMAIL PROTECTED]; Wed,
25 Aug 1999 18:56:29 -0400
Received:
(from ipic@localhost) by hospedando.com (8.9.3/8.9.3)
id SAA11141 for
[EMAIL PROTECTED]; Wed, 25 Aug 1999 18:56:28
- -0400
Received:
from mail.pplmail.com (postfix@[208.203.130.231]) by
hospedando.com (8.9.3/8.9.3) with ESMTP id
SAA11137 for <[EMAIL PROTECTED]>; Wed, 25 Aug 1999
18:56:28 -0400
Received:
from listserv.funet.fi (listserv.funet.fi
[128.214.248.27]) by mail.pplmail.com (Postfix) with ESMTP id
2945A80007 for <[EMAIL PROTECTED]>; Wed, 25 Aug 1999
17:44:20 -0400 (EDT)
Received:
from vger.rutgers.edu ([128.6.190.2]:12303 "EHLO
vger.rutgers.edu") by listserv.funet.fi with
ESMTP id <S12251AbPHYWiC>; Thu, 26 Aug 1999 01:38:02
+0300
Received:
by vger.rutgers.edu via listexpand id
<S154608AbPHYWhB>; Wed, 25 Aug 1999 18:37:01 -0400
Received:
by vger.rutgers.edu id <S154328AbPHYWev>; Wed, 25 Aug
1999 18:34:51 -0400
Received:
from runyon.cygnus.com ([205.180.230.5]:34687 "EHLO
cygnus.com") by vger.rutgers.edu with
ESMTP id <S154589AbPHYWdZ>; Wed, 25 Aug 1999 18:33:25
- -0400
Received:
from otr.mynet (dialin-sv-02.cygnus.com
[205.180.231.52]) by runyon.cygnus.com
(8.8.7-cygnus/8.8.7) with ESMTP id PAA05569 for
<[EMAIL PROTECTED]>; Wed, 25 Aug
1999 15:33:23 -0700 (PDT)
Received:
(from drepper@localhost) by otr.mynet
(8.9.3/8.9.3/ud-990718) id PAA08429; Wed, 25 Aug 1999
15:30:53 -0700
A:
VGER gcc list <[EMAIL PROTECTED]>
Asunto:
glibc 2.1.2pre3
Responder a:
[EMAIL PROTECTED] (Ulrich Drepper)
X-fingerprint:
BE 3B 21 04 BC 77 AC F0 61 92 E4 CB AC DD B9 5A
Mime-Version:
1.0 (generated by tm-edit 7.108)
Content-Type:
text/plain; charset=US-ASCII
De:
Ulrich Drepper <[EMAIL PROTECTED]>
Fecha:
25 Aug 1999 15:06:56 -0700
X-Mailer:
Gnus v5.6.45/XEmacs 21.1 - "Big Bend"
ID del mensaje:
<[EMAIL PROTECTED]>
Lines:
40
Remitente:
[EMAIL PROTECTED]
Precedence:
bulk
X-Loop:
[EMAIL PROTECTED]
X-Orcpt:
rfc822;linux-gcc-outgoing-dig
X-PopulousMail:
---------------------------------------------- Sent By
PplMail.com FREE Email Get your FREE POP
email at www.Pplmail.com
- ----------------------------------------------
X-Mozilla-Status:
8003
X-Mozilla-Status2:
00000000
X-UIDL:
B0008521608.MSG
I've uploaded the third prerelease for glibc 2.1.2 to
ftp://sourceware.cygnus.com/pub/glibc
and
ftp://ftp.XX.kernel.org/pub/software/libs/glibc
(where XX is your country code). It soon will also be available on
ftp://alpha.gnu.org/gnu/libc
There you will find the files
glibc-2.1.2pre3.tar.gz
glibc-linuxthreads-2.1.2pre3.tar.gz
and possibly .bz2 versions. There is no new crypt add-on, still use
the version released with glibc 2.1.
Since 2.1.2pre2 we've added lots of changes, especially a number of
patches went in which correct problems with threads. If no problems
are reported I'll make a final 2.1.2 release soon.
So, now is your chance to avoid releasing a buggy version. The
feedback I got for the last prereleases was lousy at best. It might
even be that this version does not even compile on some platforms.
I only have easy access to an x86 and Arm machine (well, there is the
HP but HPPA/Linux does not yet work). So you have to do the tests for
other platforms yourself or put one of the machines you care about
under my desk.
So, test this version and send feedback to
[EMAIL PROTECTED]
- --
- ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
- --------------19854CD2442E19228C3F57D4
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Return-path: <[EMAIL PROTECTED]>
Received: from hospedando.com (unverified [209.239.32.10]) by mailsvr2.telebot.net
(Rockliffe SMTPRA 3.4.2) with ESMTP id <[EMAIL PROTECTED]> for
<[EMAIL PROTECTED]>;
Wed, 25 Aug 1999 15:52:19 -0700
Received: (from ipic@localhost)
by hospedando.com (8.9.3/8.9.3) id SAA11148
for [EMAIL PROTECTED]; Wed, 25 Aug 1999 18:56:29 -0400
Received: (from ipic@localhost)
by hospedando.com (8.9.3/8.9.3) id SAA11141
for [EMAIL PROTECTED]; Wed, 25 Aug 1999 18:56:28 -0400
Received: from mail.pplmail.com (postfix@[208.203.130.231])
by hospedando.com (8.9.3/8.9.3) with ESMTP id SAA11137
for <[EMAIL PROTECTED]>; Wed, 25 Aug 1999 18:56:28 -0400
Received: from listserv.funet.fi (listserv.funet.fi [128.214.248.27])
by mail.pplmail.com (Postfix) with ESMTP id 2945A80007
for <[EMAIL PROTECTED]>; Wed, 25 Aug 1999 17:44:20 -0400 (EDT)
Received: from vger.rutgers.edu ([128.6.190.2]:12303 "EHLO vger.rutgers.edu")
by listserv.funet.fi with ESMTP id <S12251AbPHYWiC>;
Thu, 26 Aug 1999 01:38:02 +0300
Received: by vger.rutgers.edu via listexpand id <S154608AbPHYWhB>;
Wed, 25 Aug 1999 18:37:01 -0400
Received: by vger.rutgers.edu id <S154328AbPHYWev>;
Wed, 25 Aug 1999 18:34:51 -0400
Received: from runyon.cygnus.com ([205.180.230.5]:34687 "EHLO cygnus.com")
by vger.rutgers.edu with ESMTP id <S154589AbPHYWdZ>;
Wed, 25 Aug 1999 18:33:25 -0400
Received: from otr.mynet (dialin-sv-02.cygnus.com [205.180.231.52])
by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id PAA05569
for <[EMAIL PROTECTED]>; Wed, 25 Aug 1999 15:33:23 -0700 (PDT)
Received: (from drepper@localhost) by otr.mynet (8.9.3/8.9.3/ud-990718) id PAA08429;
Wed, 25 Aug 1999 15:30:53 -0700
To: VGER gcc list <[EMAIL PROTECTED]>
Subject: glibc 2.1.2pre3
Reply-To: [EMAIL PROTECTED] (Ulrich Drepper)
X-fingerprint: BE 3B 21 04 BC 77 AC F0 61 92 E4 CB AC DD B9 5A
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Ulrich Drepper <[EMAIL PROTECTED]>
Date: 25 Aug 1999 15:06:56 -0700
X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Big Bend"
Message-ID: <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
Precedence: bulk
X-Loop: [EMAIL PROTECTED]
X-Orcpt: rfc822;linux-gcc-outgoing-dig
X-PopulousMail: ----------------------------------------------
Sent By PplMail.com FREE Email
Get your FREE POP email at www.Pplmail.com
----------------------------------------------
X-Mozilla-Status2: 00000000
I've uploaded the third prerelease for glibc 2.1.2 to
ftp://sourceware.cygnus.com/pub/glibc
and
ftp://ftp.XX.kernel.org/pub/software/libs/glibc
(where XX is your country code). It soon will also be available on
ftp://alpha.gnu.org/gnu/libc
There you will find the files
glibc-2.1.2pre3.tar.gz
glibc-linuxthreads-2.1.2pre3.tar.gz
and possibly .bz2 versions. There is no new crypt add-on, still use
the version released with glibc 2.1.
Since 2.1.2pre2 we've added lots of changes, especially a number of
patches went in which correct problems with threads. If no problems
are reported I'll make a final 2.1.2 release soon.
So, now is your chance to avoid releasing a buggy version. The
feedback I got for the last prereleases was lousy at best. It might
even be that this version does not even compile on some platforms.
I only have easy access to an x86 and Arm machine (well, there is the
HP but HPPA/Linux does not yet work). So you have to do the tests for
other platforms yourself or put one of the machines you care about
under my desk.
So, test this version and send feedback to [EMAIL PROTECTED]
- --
- ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
- --------------19854CD2442E19228C3F57D4--
------------------------------
From: Internet Business <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 1999 01:10:43 +0200
Subject: Re: glibc 2.1.2pre3
Ulrich Drepper ha escrito:
> I've uploaded the third prerelease for glibc 2.1.2 to
>
> ftp://sourceware.cygnus.com/pub/glibc
> and
> ftp://ftp.XX.kernel.org/pub/software/libs/glibc
>
> (where XX is your country code). It soon will also be available on
>
> ftp://alpha.gnu.org/gnu/libc
>
> There you will find the files
>
> glibc-2.1.2pre3.tar.gz
> glibc-linuxthreads-2.1.2pre3.tar.gz
>
> and possibly .bz2 versions. There is no new crypt add-on, still use
> the version released with glibc 2.1.
>
> Since 2.1.2pre2 we've added lots of changes, especially a number of
> patches went in which correct problems with threads. If no problems
> are reported I'll make a final 2.1.2 release soon.
>
> So, now is your chance to avoid releasing a buggy version. The
> feedback I got for the last prereleases was lousy at best. It might
> even be that this version does not even compile on some platforms.
>
> I only have easy access to an x86 and Arm machine (well, there is the
> HP but HPPA/Linux does not yet work). So you have to do the tests for
> other platforms yourself or put one of the machines you care about
> under my desk.
>
> So, test this version and send feedback to [EMAIL PROTECTED]
>
> --
> ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: Internet Business <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 1999 01:10:51 +0200
Subject: Re: glibc 2.1.2pre3
Ulrich Drepper ha escrito:
> I've uploaded the third prerelease for glibc 2.1.2 to
>
> ftp://sourceware.cygnus.com/pub/glibc
> and
> ftp://ftp.XX.kernel.org/pub/software/libs/glibc
>
> (where XX is your country code). It soon will also be available on
>
> ftp://alpha.gnu.org/gnu/libc
>
> There you will find the files
>
> glibc-2.1.2pre3.tar.gz
> glibc-linuxthreads-2.1.2pre3.tar.gz
>
> and possibly .bz2 versions. There is no new crypt add-on, still use
> the version released with glibc 2.1.
>
> Since 2.1.2pre2 we've added lots of changes, especially a number of
> patches went in which correct problems with threads. If no problems
> are reported I'll make a final 2.1.2 release soon.
>
> So, now is your chance to avoid releasing a buggy version. The
> feedback I got for the last prereleases was lousy at best. It might
> even be that this version does not even compile on some platforms.
>
> I only have easy access to an x86 and Arm machine (well, there is the
> HP but HPPA/Linux does not yet work). So you have to do the tests for
> other platforms yourself or put one of the machines you care about
> under my desk.
>
> So, test this version and send feedback to [EMAIL PROTECTED]
>
> --
> ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: Internet Business <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 1999 01:10:59 +0200
Subject: Re: glibc 2.1.2pre3
Ulrich Drepper ha escrito:
> I've uploaded the third prerelease for glibc 2.1.2 to
>
> ftp://sourceware.cygnus.com/pub/glibc
> and
> ftp://ftp.XX.kernel.org/pub/software/libs/glibc
>
> (where XX is your country code). It soon will also be available on
>
> ftp://alpha.gnu.org/gnu/libc
>
> There you will find the files
>
> glibc-2.1.2pre3.tar.gz
> glibc-linuxthreads-2.1.2pre3.tar.gz
>
> and possibly .bz2 versions. There is no new crypt add-on, still use
> the version released with glibc 2.1.
>
> Since 2.1.2pre2 we've added lots of changes, especially a number of
> patches went in which correct problems with threads. If no problems
> are reported I'll make a final 2.1.2 release soon.
>
> So, now is your chance to avoid releasing a buggy version. The
> feedback I got for the last prereleases was lousy at best. It might
> even be that this version does not even compile on some platforms.
>
> I only have easy access to an x86 and Arm machine (well, there is the
> HP but HPPA/Linux does not yet work). So you have to do the tests for
> other platforms yourself or put one of the machines you care about
> under my desk.
>
> So, test this version and send feedback to [EMAIL PROTECTED]
>
> --
> ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: Internet Business <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 1999 01:31:49 +0200
Subject: Re: glibc 2.1.2pre3
Internet Business ha escrito:
> Ulrich Drepper ha escrito:
>
> > I've uploaded the third prerelease for glibc 2.1.2 to
> >
> > ftp://sourceware.cygnus.com/pub/glibc
> > and
> > ftp://ftp.XX.kernel.org/pub/software/libs/glibc
> >
> > (where XX is your country code). It soon will also be available on
> >
> > ftp://alpha.gnu.org/gnu/libc
> >
> > There you will find the files
> >
> > glibc-2.1.2pre3.tar.gz
> > glibc-linuxthreads-2.1.2pre3.tar.gz
> >
> > and possibly .bz2 versions. There is no new crypt add-on, still use
> > the version released with glibc 2.1.
> >
> > Since 2.1.2pre2 we've added lots of changes, especially a number of
> > patches went in which correct problems with threads. If no problems
> > are reported I'll make a final 2.1.2 release soon.
> >
> > So, now is your chance to avoid releasing a buggy version. The
> > feedback I got for the last prereleases was lousy at best. It might
> > even be that this version does not even compile on some platforms.
> >
> > I only have easy access to an x86 and Arm machine (well, there is the
> > HP but HPPA/Linux does not yet work). So you have to do the tests for
> > other platforms yourself or put one of the machines you care about
> > under my desk.
> >
> > So, test this version and send feedback to [EMAIL PROTECTED]
> >
> > --
> > ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> > Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> > Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: Internet Business <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 1999 01:32:47 +0200
Subject: Re: glibc 2.1.2pre3
Internet Business ha escrito:
> Ulrich Drepper ha escrito:
>
> > I've uploaded the third prerelease for glibc 2.1.2 to
> >
> > ftp://sourceware.cygnus.com/pub/glibc
> > and
> > ftp://ftp.XX.kernel.org/pub/software/libs/glibc
> >
> > (where XX is your country code). It soon will also be available on
> >
> > ftp://alpha.gnu.org/gnu/libc
> >
> > There you will find the files
> >
> > glibc-2.1.2pre3.tar.gz
> > glibc-linuxthreads-2.1.2pre3.tar.gz
> >
> > and possibly .bz2 versions. There is no new crypt add-on, still use
> > the version released with glibc 2.1.
> >
> > Since 2.1.2pre2 we've added lots of changes, especially a number of
> > patches went in which correct problems with threads. If no problems
> > are reported I'll make a final 2.1.2 release soon.
> >
> > So, now is your chance to avoid releasing a buggy version. The
> > feedback I got for the last prereleases was lousy at best. It might
> > even be that this version does not even compile on some platforms.
> >
> > I only have easy access to an x86 and Arm machine (well, there is the
> > HP but HPPA/Linux does not yet work). So you have to do the tests for
> > other platforms yourself or put one of the machines you care about
> > under my desk.
> >
> > So, test this version and send feedback to [EMAIL PROTECTED]
> >
> > --
> > ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> > Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> > Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: Internet Business <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 1999 01:32:06 +0200
Subject: Re: SPAM
Internet Business ha escrito:
> Return-path:
> <[EMAIL PROTECTED]>
> Received:
> from hospedando.com (unverified [209.239.32.10]) by
> mailsvr2.telebot.net (Rockliffe SMTPRA
> 3.4.2) with ESMTP id <[EMAIL PROTECTED]>
> for <[EMAIL PROTECTED]>; Wed, 25
> Aug 1999 15:52:19 -0700
> Received:
> (from ipic@localhost) by hospedando.com (8.9.3/8.9.3)
> id SAA11148 for [EMAIL PROTECTED]; Wed,
> 25 Aug 1999 18:56:29 -0400
> Received:
> (from ipic@localhost) by hospedando.com (8.9.3/8.9.3)
> id SAA11141 for
> [EMAIL PROTECTED]; Wed, 25 Aug 1999 18:56:28
> -0400
> Received:
> from mail.pplmail.com (postfix@[208.203.130.231]) by
> hospedando.com (8.9.3/8.9.3) with ESMTP id
> SAA11137 for <[EMAIL PROTECTED]>; Wed, 25 Aug 1999
> 18:56:28 -0400
> Received:
> from listserv.funet.fi (listserv.funet.fi
> [128.214.248.27]) by mail.pplmail.com (Postfix) with ESMTP id
> 2945A80007 for <[EMAIL PROTECTED]>; Wed, 25 Aug 1999
> 17:44:20 -0400 (EDT)
> Received:
> from vger.rutgers.edu ([128.6.190.2]:12303 "EHLO
> vger.rutgers.edu") by listserv.funet.fi with
> ESMTP id <S12251AbPHYWiC>; Thu, 26 Aug 1999 01:38:02
> +0300
> Received:
> by vger.rutgers.edu via listexpand id
> <S154608AbPHYWhB>; Wed, 25 Aug 1999 18:37:01 -0400
> Received:
> by vger.rutgers.edu id <S154328AbPHYWev>; Wed, 25 Aug
> 1999 18:34:51 -0400
> Received:
> from runyon.cygnus.com ([205.180.230.5]:34687 "EHLO
> cygnus.com") by vger.rutgers.edu with
> ESMTP id <S154589AbPHYWdZ>; Wed, 25 Aug 1999 18:33:25
> -0400
> Received:
> from otr.mynet (dialin-sv-02.cygnus.com
> [205.180.231.52]) by runyon.cygnus.com
> (8.8.7-cygnus/8.8.7) with ESMTP id PAA05569 for
> <[EMAIL PROTECTED]>; Wed, 25 Aug
> 1999 15:33:23 -0700 (PDT)
> Received:
> (from drepper@localhost) by otr.mynet
> (8.9.3/8.9.3/ud-990718) id PAA08429; Wed, 25 Aug 1999
> 15:30:53 -0700
> A:
> VGER gcc list <[EMAIL PROTECTED]>
> Asunto:
> glibc 2.1.2pre3
> Responder a:
> [EMAIL PROTECTED] (Ulrich Drepper)
> X-fingerprint:
> BE 3B 21 04 BC 77 AC F0 61 92 E4 CB AC DD B9 5A
> Mime-Version:
> 1.0 (generated by tm-edit 7.108)
> Content-Type:
> text/plain; charset=US-ASCII
> De:
> Ulrich Drepper <[EMAIL PROTECTED]>
> Fecha:
> 25 Aug 1999 15:06:56 -0700
> X-Mailer:
> Gnus v5.6.45/XEmacs 21.1 - "Big Bend"
> ID del mensaje:
> <[EMAIL PROTECTED]>
> Lines:
> 40
> Remitente:
> [EMAIL PROTECTED]
> Precedence:
> bulk
> X-Loop:
> [EMAIL PROTECTED]
> X-Orcpt:
> rfc822;linux-gcc-outgoing-dig
> X-PopulousMail:
> ---------------------------------------------- Sent By
> PplMail.com FREE Email Get your FREE POP
> email at www.Pplmail.com
> ----------------------------------------------
> X-Mozilla-Status:
> 8003
> X-Mozilla-Status2:
> 00000000
> X-UIDL:
> B0008521608.MSG
>
> I've uploaded the third prerelease for glibc 2.1.2 to
>
> ftp://sourceware.cygnus.com/pub/glibc
> and
> ftp://ftp.XX.kernel.org/pub/software/libs/glibc
>
> (where XX is your country code). It soon will also be available on
>
> ftp://alpha.gnu.org/gnu/libc
>
> There you will find the files
>
> glibc-2.1.2pre3.tar.gz
> glibc-linuxthreads-2.1.2pre3.tar.gz
>
> and possibly .bz2 versions. There is no new crypt add-on, still use
> the version released with glibc 2.1.
>
> Since 2.1.2pre2 we've added lots of changes, especially a number of
> patches went in which correct problems with threads. If no problems
> are reported I'll make a final 2.1.2 release soon.
>
> So, now is your chance to avoid releasing a buggy version. The
> feedback I got for the last prereleases was lousy at best. It might
> even be that this version does not even compile on some platforms.
>
> I only have easy access to an x86 and Arm machine (well, there is the
> HP but HPPA/Linux does not yet work). So you have to do the tests for
> other platforms yourself or put one of the machines you care about
> under my desk.
>
> So, test this version and send feedback to
> [EMAIL PROTECTED]
>
> --
> ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> Cygnus Solutions `--' drepper at cygnus.com `------------------------
>
> ------------------------------------------------------------------------
>
> Asunto: glibc 2.1.2pre3
> Fecha: 25 Aug 1999 15:06:56 -0700
> De: Ulrich Drepper <[EMAIL PROTECTED]>
> A: VGER gcc list <[EMAIL PROTECTED]>
>
> I've uploaded the third prerelease for glibc 2.1.2 to
>
> ftp://sourceware.cygnus.com/pub/glibc
> and
> ftp://ftp.XX.kernel.org/pub/software/libs/glibc
>
> (where XX is your country code). It soon will also be available on
>
> ftp://alpha.gnu.org/gnu/libc
>
> There you will find the files
>
> glibc-2.1.2pre3.tar.gz
> glibc-linuxthreads-2.1.2pre3.tar.gz
>
> and possibly .bz2 versions. There is no new crypt add-on, still use
> the version released with glibc 2.1.
>
> Since 2.1.2pre2 we've added lots of changes, especially a number of
> patches went in which correct problems with threads. If no problems
> are reported I'll make a final 2.1.2 release soon.
>
> So, now is your chance to avoid releasing a buggy version. The
> feedback I got for the last prereleases was lousy at best. It might
> even be that this version does not even compile on some platforms.
>
> I only have easy access to an x86 and Arm machine (well, there is the
> HP but HPPA/Linux does not yet work). So you have to do the tests for
> other platforms yourself or put one of the machines you care about
> under my desk.
>
> So, test this version and send feedback to [EMAIL PROTECTED]
>
> --
> ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: Internet Business <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 1999 01:32:34 +0200
Subject: Re: glibc 2.1.2pre3
Internet Business ha escrito:
> Ulrich Drepper ha escrito:
>
> > I've uploaded the third prerelease for glibc 2.1.2 to
> >
> > ftp://sourceware.cygnus.com/pub/glibc
> > and
> > ftp://ftp.XX.kernel.org/pub/software/libs/glibc
> >
> > (where XX is your country code). It soon will also be available on
> >
> > ftp://alpha.gnu.org/gnu/libc
> >
> > There you will find the files
> >
> > glibc-2.1.2pre3.tar.gz
> > glibc-linuxthreads-2.1.2pre3.tar.gz
> >
> > and possibly .bz2 versions. There is no new crypt add-on, still use
> > the version released with glibc 2.1.
> >
> > Since 2.1.2pre2 we've added lots of changes, especially a number of
> > patches went in which correct problems with threads. If no problems
> > are reported I'll make a final 2.1.2 release soon.
> >
> > So, now is your chance to avoid releasing a buggy version. The
> > feedback I got for the last prereleases was lousy at best. It might
> > even be that this version does not even compile on some platforms.
> >
> > I only have easy access to an x86 and Arm machine (well, there is the
> > HP but HPPA/Linux does not yet work). So you have to do the tests for
> > other platforms yourself or put one of the machines you care about
> > under my desk.
> >
> > So, test this version and send feedback to [EMAIL PROTECTED]
> >
> > --
> > ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> > Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> > Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: Burak Serdar <[EMAIL PROTECTED]>
Date: Wed, 25 Aug 1999 21:23:58 -0400
Subject: Re: arrays that are too big
Berkeley Hynes wrote:
> What is the standard behaviour of a compiled C program which declares an
> array which is too big given the system's available memory?
>
> Whenever I use dynamic memeory I always test for malloc's error codes,
> but it occurred to me that I don't test anything to make sure an array
> has been properly allocated. Should I be testing something?
>
> Thanks in advance,
>
> Berkeley Hynes
> [EMAIL PROTECTED]
The system should not be able to load the program if it does not fit into
memory. If the program is running, it means that all the static variables
are 'allocated'.
------------------------------
From: Burak Serdar <[EMAIL PROTECTED]>
Date: Wed, 25 Aug 1999 21:25:43 -0400
Subject: Re: Prblem compiling C++ with G++
Andres Tarallo wrote:
> I've developed a small class in C++; while compiling it I'm getting
> the following message
> "return type specification for constructor invalid".
>
> I don't understand this message, what does it mean?. As far as I'm
> concerned the constructor does not return anything.
>
> Thanks in advance
> Andres Tarallo
How did you declare the constructor? It should not return anything - it
should not be even 'void'
------------------------------
From: Fenglou Mao <[EMAIL PROTECTED]>
Date: Thu, 26 Aug 1999 10:19:55 -0700 (PDT)
Subject: Re: arrays that are too big
static float array[10000000];
^^^^^^
On Wed, 25 Aug 1999, Berkeley Hynes wrote:
> What is the standard behaviour of a compiled C program which declares an
> array which is too big given the system's available memory?
>
> Whenever I use dynamic memeory I always test for malloc's error codes,
> but it occurred to me that I don't test anything to make sure an array
> has been properly allocated. Should I be testing something?
>
> Thanks in advance,
>
> Berkeley Hynes
> [EMAIL PROTECTED]
>
Sincerely Yours,
FengLou Mao
*******************************
ADD:Mr. FengLou Mao
Peking University
BeiJing
P.R.China
Tel:86-10-62751490
Fax:86-10-62756833
------------------------------
From: Michael Eyrich <[EMAIL PROTECTED]>
Date: Thu, 26 Aug 1999 15:07:24 +0200 (CEST)
Subject: Re: arrays that are too big
On Wed, 25 Aug 1999, Burak Serdar wrote:
|Berkeley Hynes wrote:
|
|> What is the standard behaviour of a compiled C program which declares an
|> array which is too big given the system's available memory?
|>
|> Whenever I use dynamic memeory I always test for malloc's error codes,
|> but it occurred to me that I don't test anything to make sure an array
|> has been properly allocated. Should I be testing something?
|>
|> Thanks in advance,
|>
|> Berkeley Hynes
|> [EMAIL PROTECTED]
|
| The system should not be able to load the program if it does not fit into
|memory. If the program is running, it means that all the static variables
|are 'allocated'.
AFAIK the memory is virtually allocated, not physically. Real allocation
takes places, when the memory is used. Am I wrong?
Michael.
- --
Michael Eyrich, PRZ, TU-Berlin
[EMAIL PROTECTED]
------------------------------
From: George Drumea <[EMAIL PROTECTED]>
Date: Thu, 26 Aug 1999 23:50:21 +0300
Subject: Re: arrays that are too big
Fenglou Mao wrote:
> static float array[10000000];
> ^^^^^^
IIRC, static applied to a global valiable means that the variable can be used
only in the current module. So static affects the scope of the variable, and
has nothing to do with memory allocation. `static int v[100]' is the same with
`int v[100]' in a single module program. If static is applied to a local
variable in a function, then the variable is preserved between different
calls.
In the matter of the init of the array, if the program loads then the array is
ok. (arrays generally exist within the program -
except if you use -fconserve-space wich is a different case)
Bye.
- --
Send money to [EMAIL PROTECTED] and prayers to [EMAIL PROTECTED]
For the latest version of the Bible (currently 3.5.18) do a ftp
at ftp.heaven.com, username: religious_one, password: god_rules
And remember: God uses Linux2.
------------------------------
From: Fenglou Mao <[EMAIL PROTECTED]>
Date: Fri, 27 Aug 1999 08:31:41 -0700 (PDT)
Subject: Re: arrays that are too big
If you don't use "static", your array is allocated in the call stack, I
think, "static" also make your array allocated in the globe memory. You
can write a small program, it has a large array, a loop asign value to
all the elements, then you can find the difference.
In slackware3.4, gcc 2.7.2, largest array is about 8M if no "static",
it can reach your "physical memory" + "virtual memory" size if you use
"static".
>
>
> Fenglou Mao wrote:
>
> > static float array[10000000];
> > ^^^^^^
>
> IIRC, static applied to a global valiable means that the variable can be used
> only in the current module. So static affects the scope of the variable, and
> has nothing to do with memory allocation. `static int v[100]' is the same with
> `int v[100]' in a single module program. If static is applied to a local
> variable in a function, then the variable is preserved between different
> calls.
> In the matter of the init of the array, if the program loads then the array is
> ok. (arrays generally exist within the program -
> except if you use -fconserve-space wich is a different case)
>
> Bye.
> --
> Send money to [EMAIL PROTECTED] and prayers to [EMAIL PROTECTED]
> For the latest version of the Bible (currently 3.5.18) do a ftp
> at ftp.heaven.com, username: religious_one, password: god_rules
> And remember: God uses Linux2.
>
>
Sincerely Yours,
FengLou Mao
*******************************
ADD:Mr. FengLou Mao
Peking University
BeiJing
P.R.China
Tel:86-10-62751490
Fax:86-10-62756833
------------------------------
From: [EMAIL PROTECTED] (H.J. Lu)
Date: Tue, 31 Aug 1999 14:28:52 -0700 (PDT)
Subject: binutils 2.9.5.0.10 is released.
This is the beta release of binutils 2.9.5.0.10 for Linux, which is
based on binutils 1999 0831 plus various changes. It is purely for
Linux, although it has been tested on Solaris/Sparc and Solaris/x86
from time to time.
I am planning to make the public release soon. Please test it as much
as you can.
Please report any bugs related to binutils 2.9.5.0.10 to [EMAIL PROTECTED]
For arm-linux targets, there are some important differences in behaviour
between these tools and binutils 2.9.1.0.x. The linker emulation name has
changed from elf32arm{26} to armelf_linux{26}. Also, the "-p" flag must be
passed with the linker when working with object files (or static libraries)
created using older versions of the assembler. If this flag is omitted the
linker will silently generate bad output when given old input files.
To get the correct behaviour from gcc, amend the *link section of your specs
file as follows:
*link:
%{h*} %{version:-v} %{b} %{Wl,*:%*} %{static:-Bstatic} %{shared:-shared
} %{symbolic:-Bsymbolic} %{rdynamic:-export-dynamic} %{!dynamic-linker:
- -dynamic-linker /lib/ld-linux.so.2} -X %{mbig-endian:-EB} %{mapcs-26:-m ar
melf_linux26} %{!mapcs-26:-m armelf_linux} -p
Changes from binutils 2.9.5.0.8:
1. Update from binutils 1999 0831. It allows spaces around '(' and ')'
in x86 FP register names.
Changes from binutils 2.9.5.0.7:
1. Update from binutils 1999 0821.
2. Some MIPS changes.
Changes from binutils 2.9.5.0.6:
1. Update from binutils 1999 0813.
2. i370 update.
Changes from binutils 2.9.5.0.5:
1. Update from binutils 1999 0809. An ELF/Sparc ld bug is fixed.
Changes from binutils 2.9.5.0.4:
1. Update from binutils 1999 0806. A Solaris/Sparc gas bug is fixed.
2. Remove mips gas patches from binutils 2.9.1.0.25.
Changes from binutils 2.9.5.0.3:
1. Update from binutils 1999 0801.
2. Support for real mode x86 gcc.
Changes from binutils 2.9.4.0.8:
1. Update from binutils 1999 0719. A libc 5 related bug fix.
2. Fix a typo in mips gas.
Changes from binutils 2.9.4.0.7:
1. Update from binutils 1999 0710. A weak symbol bug
http://egcs.cygnus.com/ml/egcs-bugs/1999-07/msg00129.html
is fixed.
Changes from binutils 2.9.4.0.6:
1. Update from binutils 1999 0626.
Changes from binutils 2.9.4.0.5:
1. Update from binutils 1999 0620.
2. Remove my fwait fix and use the one in cvs.
3. Use "--only-section=section" instead of "--extract-section=section".
for objcopy.
Changes from binutils 2.9.4.0.4:
1. Update from binutils 1999 0612.
2. Remove various temporary fixes of mine since those bugs are fixed
now.
Changes from binutils 2.9.4.0.3:
1. Update from binutils 1999 0611.
2. Remove my ELF/Alpha bfd changes.
3. Use the local symbol copy fix in binutils 1999 0611.
Changes from binutils 2.9.4.0.2:
1. Update from binutils 1999 0607.
2. Remove my Sparc hacks.
3. Fix local symbol copy.
Changes from binutils 2.9.4.0.1:
1. Update from binutils 1999 0606.
2. Restore relocation overflow checking in binutils 2.9.1.0.25 so that
Linux kernel can build.
3. Fix i370 for the new gas.
Changes from binutils 1999 0605:
1. Fix a -Bsymbolic bug for Linux/alpha.
2. Add ELF/i370.
3. Fix 8/16-bit relocations for i386.
4. Add --redefine-sym=old_form=new_form to objcopy.
5. Add "-j section" for objcopy.
6. Fix i386 disassembler for fwait.
7. Fix a Sparc asm bug.
8. Add Ada demangle support.
9. Fix MIPS/ELF bugs.
10. Add some vxworks suppport.
11. Fix a.out assembler.
The file list:
1. binutils-2.9.5.0.10.tar.gz. Source code.
2. binutils-2.9.5.0.8-2.9.5.0.10.diff.gz. Patch against the previous
beta source code.
3. binutils-2.9.5.0.10-1.src.rpm. Source RPM.
4. binutils-2.9.5.0.10-1.i386.rpm. X86 inary RPM for RedHat 6.0.
5. binutils-2.9.5.0.10-1.alpha.rpm. Alpha binary RPM for RedHat 6.0.
There are also bzip2 versions of tar and diff files.
The primary ftp sites for the beta Linux binutils are:
1. ftp://ftp.valinux.com/pub/support/hjl/binutils
Thanks.
H.J. Lu
[EMAIL PROTECTED]
08/31/99
------------------------------
From: Ulrich Drepper <[EMAIL PROTECTED]>
Date: 06 Sep 1999 16:21:46 -0700
Subject: glibc 2.1.2
Release 2.1.2 of the GNU C library is now available at
ftp://sourceware.cygnus.com/pub/glibc
and
ftp://ftp.XX.kernel.org/pub/software/libs/glibc
(where XX is your country code) and all the mirror sites of these
servers around the world.
It would also be available at
ftp://ftp.gnu.org/pub/gnu/glibc
but somebody removed my account on this machine. Too bad. It is
unreliable anyway.
The new files are
glibc-2.1.2.tar.gz
glibc-linuxthreads-2.1.2.tar.gz
together with a patch relative to the 2.1.1 release
glibc-2.1.1-2.1.2.diff.gz
There are also .bz2 files available which should be preferred to
preserve bandwidth.
The crypt add-on hasn't changed and therefore the version from release
2.1 should be used.
glibc-crypt-2.1.tar.gz
The crypt add-on is available from
ftp://ftp.gwdg.de/pub/linux/glibc
There is no localedata add-on anymore as there was in glibc 2.0. Don't
use the add-on from glibc 2.0, the necessary data already comes with the
main tar file.
This release of the library runs on the following targets:
*-*-gnu GNU Hurd
i[3456]86-*-linux-gnu Linux-2.x on Intel
m68k-*-linux-gnu Linux-2.x on Motorola 680x0
alpha-*-linux-gnu Linux-2.x on DEC Alpha
powerpc-*-linux-gnu Linux and MkLinux on PowerPC systems
sparc-*-linux-gnu Linux-2.x on SPARC
sparc64-*-linux-gnu Linux-2.x on UltraSPARC
arm-*-none ARM standalone systems
arm-*-linux Linux-2.x on ARM
arm-*-linuxaout Linux-2.x on ARM using a.out binaries
Work on ports to mips-*-linux-gnu, sparc-sun-solaris, and mips-sgi-irix6
are under way but need more work. Help to finish the ports is welcome.
The 2.1.2 fixes several problems from former releases and is consider
very stable and reliable. Immediately upgrading from prior versions
is encouraged.
*BUT*: updating the C library is no trivial task and it is very easy
to damage one's system. Therefore, persons who do not exactly know
what to do, should consider using a binary distribution instead, when
they become available. All major Linux distributors will hopefully
base their next release on glibc 2.1.2. Don't tell us you haven't been
warned. Another reason why not everybody should think about compiling
glibc is the disk and CPU requirements: on Intel platforms the full
build requires about 290MB plus the space you need to install it.
This number is probably higher on RISC platforms. During the
compilation the compiler will need large amounts of virtual memory.
We are talking about 100MB on Intel and 200MB on Alpha. If using the
`-j' option of make this numbers grow linearly. Compiling takes more
than 4 hours on a i586@133, and still 45 minutes on a 2xi686@233. See
the FAQ file for more numbers.
In case you decide to compile glibc yourself you need to read the file
INSTALL. It will explain among other things which tools are
necessary. The most important one is the compiler. Although other
versions might work it is recommended to get gcc 2.96. But see the
FAQ for expected failures. In case of a problem during the
compilation with a compiler other than gcc 2.96 get the recommended
version first (at http://sourceware.cygnus.com). This is especially
true for gcc 2.7.2.3 which (some people believe) is a usable compiler.
But in fact it is extremely buggy and will definitely fail to compile
glibc on every platform.
The 2.1.2 release should be binary compatible with the 2.0 release.
All programs should continue to run. There are only a few exceptions:
- - some shared libraries have to be updated as well. They are using
details from the libc. These libraries include the C++ library
(libstdc++) and the curses library. See the FAQ for more information.
Programs using these libraries are not effected. The number of
problems should be significantly lower with the 2.1.2 release than
they were with 2.1 and 2.1.1.
- - some programs use *internal* symbols of the C library. These names of
these symbols all start with an underscore and the reason why these
symbols are "internal" is because they change or might fall away in
new versions of the library. And this did happen a lot. Don't even
think about complaining on the libc lists about this, the programmers
of these applications made the errors. We have now mechanisms in
place which will prevent this from happening again even in the presence
of programmers unwilling to follow the rules.
For people using old pre-2.0 snapshots (this particularly affects
PowerPC users, for a while the standard glibc on powerpc was a 961212
snapshot), note that all 2.x versions are binary incompatible with
pre-2.0 snapshots. In general, binary compatibility is not guaranteed
if you use unreleased versions of glibc.
Problems should all be reported using the `glibcbug' shell script. Simply
run this script, fill out the information and you are set. If at the time
you start the script it complains like this
/usr/bin/glibcbug: emacs: command not found
simply set one of the environment variables EDITOR and VISUAL (this should
happen on every system automatically):
env EDITOR=vi glibcbug
Before sending a bug report make sure you have read the BUGS and the
FAQ file which come with the glibc sources. You won't even get an
answer if it is obvious you haven't read these files. It is also
helpful to scan the appropriate newsgroups and mailing lists to see
whether somebody else already had this problem. We also have a bug
report database with an web interface at
http://www-gnats.gnu.ai.mit.edu:8080/cgi-bin/wwwgnats.pl
It is very easy to browse and chances are somebody already reported
the problem. There is another thing we don't want to hear about: the
size. glibc is big, but this is necessary for a multi-platform Unix
library.
For this release I fortunately again could count on the help of
several people. In purely random order:
Mark Kettenis
Geoff Keating
Christian Gafton
Zack Weinberg
Thorsten Kukuk
Andreas Schwab
Roland McGrath
Richard Henderson
Philip Blundell
Andreas Jaeger
H.J. Lu
The list with the changes below contains a few more names. Please
remember those names for the day you have the opportunity to thank
them.
Changes include:
- - corrections to math functions
- - nscd works on SPARC ad Alpha
- - malloc checks parameter
- - many Hurd changes
- - printf function fixes (mostly wide char related)
- - header cleanups
- - performance improvements
- - dynamic memory cleanups
- - correct return values of reentrant netdb functions (returns now error
code, not -1). Attention when recompiling X since it uses these
functions incorrectly.
- - fix some wide character string functions
- - documentation updates
- - cookie stdio streams now work
- - getaddrinfo should work now
- - the dynamic loader should now be absolutely thread-safe
- - several character set conversion modules were corrected
- - librt works a bit better despite the broken signal handling model of
the Linux kernel
- - putenv corrected according to common practice and standards
(programs using putenv incorrectly might have some problems)
- - some security fixes
- - many more bug fixes
There is no reported bug left which can be fixed in this release.
There are only a few bigger (and non-critical) problems left which
either wait for a volunteer to be done or will be fixed with the glibc
2.2 release.
- --
- ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: [EMAIL PROTECTED] (H.J. Lu)
Date: Mon, 6 Sep 1999 16:39:09 -0700 (PDT)
Subject: binutils 2.9.5.0.11 is released.
This is the beta release of binutils 2.9.5.0.11 for Linux, which is
based on binutils 1999 0906 plus various changes. It is purely for
Linux, although it has been tested on Solaris/Sparc and Solaris/x86
from time to time.
I am planning to make the public release soon. Please test it as much
as you can.
Please report any bugs related to binutils 2.9.5.0.11 to [EMAIL PROTECTED]
For arm-linux targets, there are some important differences in behaviour
between these tools and binutils 2.9.1.0.x. The linker emulation name has
changed from elf32arm{26} to armelf_linux{26}. Also, the "-p" flag must be
passed with the linker when working with object files (or static libraries)
created using older versions of the assembler. If this flag is omitted the
linker will silently generate bad output when given old input files.
To get the correct behaviour from gcc, amend the *link section of your specs
file as follows:
*link:
%{h*} %{version:-v} %{b} %{Wl,*:%*} %{static:-Bstatic} %{shared:-shared
} %{symbolic:-Bsymbolic} %{rdynamic:-export-dynamic} %{!dynamic-linker:
- -dynamic-linker /lib/ld-linux.so.2} -X %{mbig-endian:-EB} %{mapcs-26:-m ar
melf_linux26} %{!mapcs-26:-m armelf_linux} -p
Changes from binutils 2.9.5.0.10:
1. Update from binutils 1999 0906. It fixed a PIC linker bug on ix86
and sparc.
2. Remove elf/hppa since it is WIP.
Changes from binutils 2.9.5.0.8:
1. Update from binutils 1999 0831. It allows spaces around '(' and ')'
in x86 FP register names.
Changes from binutils 2.9.5.0.7:
1. Update from binutils 1999 0821.
2. Some MIPS changes.
Changes from binutils 2.9.5.0.6:
1. Update from binutils 1999 0813.
2. i370 update.
Changes from binutils 2.9.5.0.5:
1. Update from binutils 1999 0809. An ELF/Sparc ld bug is fixed.
Changes from binutils 2.9.5.0.4:
1. Update from binutils 1999 0806. A Solaris/Sparc gas bug is fixed.
2. Remove mips gas patches from binutils 2.9.1.0.25.
Changes from binutils 2.9.5.0.3:
1. Update from binutils 1999 0801.
2. Support for real mode x86 gcc.
Changes from binutils 2.9.4.0.8:
1. Update from binutils 1999 0719. A libc 5 related bug fix.
2. Fix a typo in mips gas.
Changes from binutils 2.9.4.0.7:
1. Update from binutils 1999 0710. A weak symbol bug
http://egcs.cygnus.com/ml/egcs-bugs/1999-07/msg00129.html
is fixed.
Changes from binutils 2.9.4.0.6:
1. Update from binutils 1999 0626.
Changes from binutils 2.9.4.0.5:
1. Update from binutils 1999 0620.
2. Remove my fwait fix and use the one in cvs.
3. Use "--only-section=section" instead of "--extract-section=section".
for objcopy.
Changes from binutils 2.9.4.0.4:
1. Update from binutils 1999 0612.
2. Remove various temporary fixes of mine since those bugs are fixed
now.
Changes from binutils 2.9.4.0.3:
1. Update from binutils 1999 0611.
2. Remove my ELF/Alpha bfd changes.
3. Use the local symbol copy fix in binutils 1999 0611.
Changes from binutils 2.9.4.0.2:
1. Update from binutils 1999 0607.
2. Remove my Sparc hacks.
3. Fix local symbol copy.
Changes from binutils 2.9.4.0.1:
1. Update from binutils 1999 0606.
2. Restore relocation overflow checking in binutils 2.9.1.0.25 so that
Linux kernel can build.
3. Fix i370 for the new gas.
Changes from binutils 1999 0605:
1. Fix a -Bsymbolic bug for Linux/alpha.
2. Add ELF/i370.
3. Fix 8/16-bit relocations for i386.
4. Add --redefine-sym=old_form=new_form to objcopy.
5. Add "-j section" for objcopy.
6. Fix i386 disassembler for fwait.
7. Fix a Sparc asm bug.
8. Add Ada demangle support.
9. Fix MIPS/ELF bugs.
10. Add some vxworks suppport.
11. Fix a.out assembler.
The file list:
1. binutils-2.9.5.0.11.tar.gz. Source code.
2. binutils-2.9.5.0.10-2.9.5.0.11.diff.gz. Patch against the previous
beta source code.
3. binutils-2.9.5.0.11-1.src.rpm. Source RPM.
4. binutils-2.9.5.0.11-1.i386.rpm. X86 inary RPM for RedHat 6.0.
5. binutils-2.9.5.0.11-1.alpha.rpm. Alpha binary RPM for RedHat 6.0.
There are also bzip2 versions of tar and diff files.
The primary ftp sites for the beta Linux binutils are:
1. ftp://ftp.valinux.com/pub/support/hjl/binutils
Thanks.
H.J. Lu
[EMAIL PROTECTED]
09/06/99
------------------------------
From: Graham Murray <[EMAIL PROTECTED]>
Date: 07 Sep 1999 06:29:47 +0000
Subject: Re: glibc 2.1.2
Ulrich Drepper <[EMAIL PROTECTED]> writes:
> necessary. The most important one is the compiler. Although other
> versions might work it is recommended to get gcc 2.96. But see the
> FAQ for expected failures. In case of a problem during the
> compilation with a compiler other than gcc 2.96 get the recommended
> version first (at http://sourceware.cygnus.com).
Do you really mean 2.96? I already have 2.95-1 and I have seen no
announcements of 2.96, nor can I see 2.96 at sourceware.
------------------------------
From: Ulrich Drepper <[EMAIL PROTECTED]>
Date: 06 Sep 1999 23:35:05 -0700
Subject: Re: glibc 2.1.2
Graham Murray <[EMAIL PROTECTED]> writes:
> Do you really mean 2.96? I already have 2.95-1 and I have seen no
> announcements of 2.96, nor can I see 2.96 at sourceware.
You are right, it's 2.95.1.
- --
- ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
------------------------------
From: "Gabor Z. Papp" <[EMAIL PROTECTED]>
Date: Tue, 7 Sep 1999 13:53:25 +0200
Subject: Re: glibc 2.1.2
Ulrich, H.J., everybody,
gcc rpc_clntout.c -c -O -Wall -Winline -Wstrict-prototypes -Wwrite-strings -g
-I../include -I. -I.. -I../libio -I../sysdeps/i386/elf -I../crypt/sysdeps/unix
-I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread
-I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix
-I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386
-I../sysdeps/unix/sysv/linux/i386/i686 -I../sysdeps/unix/sysv/linux/i386
-I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common
-I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386
-I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/libm-i387/i686
-I../sysdeps/i386/fpu -I../sysdeps/libm-i387 -I../sysdeps/i386
-I../sysdeps/wordsize-32 -I../sysdeps/ieee754 -I../sysdeps/libm-ieee754
-I../sysdeps/generic/elf -I../sysdeps/generic -D_LIBC_REENTRANT -include
../include/libc-symbols.h -o!
!
rpc_clntout.o
gcc rpc_tblout.c -c -O -Wall -Winline -Wstrict-prototypes -Wwrite-strings -g
-I../include -I. -I.. -I../libio -I../sysdeps/i386/elf -I../crypt/sysdeps/unix
-I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread
-I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix
-I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386
-I../sysdeps/unix/sysv/linux/i386/i686 -I../sysdeps/unix/sysv/linux/i386
-I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common
-I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386
-I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/libm-i387/i686
-I../sysdeps/i386/fpu -I../sysdeps/libm-i387 -I../sysdeps/i386
-I../sysdeps/wordsize-32 -I../sysdeps/ieee754 -I../sysdeps/libm-ieee754
-I../sysdeps/generic/elf -I../sysdeps/generic -D_LIBC_REENTRANT -include
../include/libc-symbols.h -o !
!
rpc_tblout.o
gcc rpc_sample.c -c -O -Wall -Winline -Wstrict-prototypes -Wwrite-strings -g
-I../include -I. -I.. -I../libio -I../sysdeps/i386/elf -I../crypt/sysdeps/unix
-I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread
-I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix
-I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386
-I../sysdeps/unix/sysv/linux/i386/i686 -I../sysdeps/unix/sysv/linux/i386
-I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common
-I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386
-I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/libm-i387/i686
-I../sysdeps/i386/fpu -I../sysdeps/libm-i387 -I../sysdeps/i386
-I../sysdeps/wordsize-32 -I../sysdeps/ieee754 -I../sysdeps/libm-ieee754
-I../sysdeps/generic/elf -I../sysdeps/generic -D_LIBC_REENTRANT -include
../include/libc-symbols.h -o !
!
rpc_sample.o
gcc -nostdlib -nostartfiles -o rpcgen -Wl,-dynamic-linker=/lib/ld-linux.so.2
../csu/crt1.o ../csu/crti.o `gcc --print-file-name=crtbegin.o` rpc_main.o rpc_hout.o
rpc_cout.o rpc_parse.o rpc_scan.o rpc_util.o rpc_svcout.o rpc_clntout.o rpc_tblout.o
rpc_sample.o
-Wl,-rpath-link=..:../math:../elf:../nss:../nis:../db2:../rt:../resolv:../linuxthreads
../libc.so.6 ../libc_nonshared.a -lgcc `gcc --print-file-name=crtend.o` ../csu/crtn.o
gcc rpcinfo.c -c -O -Wall -Winline -Wstrict-prototypes -Wwrite-strings -g
-I../include -I. -I.. -I../libio -I../sysdeps/i386/elf -I../crypt/sysdeps/unix
-I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread
-I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix
-I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386
-I../sysdeps/unix/sysv/linux/i386/i686 -I../sysdeps/unix/sysv/linux/i386
-I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common
-I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386
-I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/libm-i387/i686
-I../sysdeps/i386/fpu -I../sysdeps/libm-i387 -I../sysdeps/i386
-I../sysdeps/wordsize-32 -I../sysdeps/ieee754 -I../sysdeps/libm-ieee754
-I../sysdeps/generic/elf -I../sysdeps/generic -D_LIBC_REENTRANT -include
../include/libc-symbols.h -o rpc!
!
info.o
gcc -nostdlib -nostartfiles -o rpcinfo -Wl,-dynamic-linker=/lib/ld-linux.so.2
../csu/crt1.o ../csu/crti.o `gcc --print-file-name=crtbegin.o` rpcinfo.o
-Wl,-rpath-link=..:../math:../elf:../nss:../nis:../db2:../rt:../resolv:../linuxthreads
../libc.so.6 ../libc_nonshared.a -lgcc `gcc --print-file-name=crtend.o` ../csu/crtn.o
../elf/ld-linux.so.2 --library-path
..:../math:../elf:../nss:../nis:../db2:../rt:../resolv:../linuxthreads ./rpcgen -Y
`gcc -print-file-name=cpp | sed "s|/cpp$||"` -c rpcsvc/bootparam_prot.x -o
xbootparam_prot.T
make[1]: *** [xbootparam_prot.stmp] Illegal instruction
make[1]: Leaving directory `/mnt/part2/src/glibc-2.1.2/sunrpc'
make: *** [sunrpc/others] Error 2
I'm compiling glibc 2.1.2
My current glibc 2.1.1, gcc 2.95.1, binutils 2.9.5.0.8, linux 2.3.16
compiled for i486-pc-linux-gnu
I try compiling glibc 2.1.2 with --host/build/target=i686-pc-linux-gnu
and I get this error. This is normal, or I have something wrong
configured? The processor is an AMD 5x86.
Also a ix86-linux-gnu related queston; at every processor upgrade I
must recompile these things with the actual ix86-pc string, or I don't
miss nothing when I use the -i486-pc-linux-gnu compiled utils on a
Pentium, PII, PIII?
------------------------------
From: Andreas Jaeger <[EMAIL PROTECTED]>
Date: 07 Sep 1999 16:02:05 +0200
Subject: Re: glibc 2.1.2
>>>>> Gabor Z Papp writes:
> Ulrich, H.J., everybody,
> I'm compiling glibc 2.1.2
and didn't read the FAQ before
> My current glibc 2.1.1, gcc 2.95.1, binutils 2.9.5.0.8, linux 2.3.16
> compiled for i486-pc-linux-gnu
> I try compiling glibc 2.1.2 with --host/build/target=i686-pc-linux-gnu
> and I get this error. This is normal, or I have something wrong
> configured? The processor is an AMD 5x86.
Read the FAQ 1.18
Andreas
- --
Andreas Jaeger [EMAIL PROTECTED] [EMAIL PROTECTED]
for pgp-key finger [EMAIL PROTECTED]
------------------------------
From: "Gabor Z. Papp" <[EMAIL PROTECTED]>
Date: Tue, 7 Sep 1999 20:41:50 +0000
Subject: glibc/binutils upgrade -> g++ reports itself as crosscompiler
I had exactly this problem after upgrading glibc from 2.0 to 2.1, but
I don't remember the solution. :-(
After upgrading glibc from 2.1.1 to 2.1.2 and
binutils from 2.9.5.0.8 to 2.9.5.11, gcc 2.95.1 reports itself as C++
crosscompiler, but not C crosscompiler. I must recompile gcc also
after a glibc upgrade?
Just found; when I define configure --host=i486-pc-linux-gnu, C++ don't
reports itself as crosscompiler. So, I'm interesting, that this is belongs
to glibc or binutils?
------------------------------
From: "Gabor Z. Papp" <[EMAIL PROTECTED]>
Date: Tue, 7 Sep 1999 20:02:14 +0000
Subject: Re: glibc 2.1.2
Andreas Jaeger <[EMAIL PROTECTED]> wrote:
| > I'm compiling glibc 2.1.2
| and didn't read the FAQ before
I do, after mailposting. :-( I'm really sorry.
| > I try compiling glibc 2.1.2 with --host/build/target=i686-pc-linux-gnu
| > and I get this error. This is normal, or I have something wrong
| > configured? The processor is an AMD 5x86.
| Read the FAQ 1.18
My real question is the reverse of this problem.
What is, when I compile a libc for better processor, like compiling
for i686 on an i486? I miss something, or not, when I use the new libc
on the i686?
I want compile a libc that usable on every i4-686 processor, and also
gcc, binutils. I must do this for every type of processor, or I can do
it on a 486, without any feature missing?
------------------------------
From: Andreas Jaeger <[EMAIL PROTECTED]>
Date: 07 Sep 1999 23:32:58 +0200
Subject: Re: glibc 2.1.2
>>>>> Gabor Z Papp writes:
Gabor> Andreas Jaeger <[EMAIL PROTECTED]> wrote:
Gabor> | > I'm compiling glibc 2.1.2
Gabor> | and didn't read the FAQ before
Gabor> I do, after mailposting. :-( I'm really sorry.
Gabor> | > I try compiling glibc 2.1.2 with --host/build/target=i686-pc-linux-gnu
Gabor> | > and I get this error. This is normal, or I have something wrong
Gabor> | > configured? The processor is an AMD 5x86.
Gabor> | Read the FAQ 1.18
Gabor> My real question is the reverse of this problem.
Gabor> What is, when I compile a libc for better processor, like compiling
Gabor> for i686 on an i486? I miss something, or not, when I use the new libc
Gabor> on the i686?
If you compile for an i686 it will only run on i686 (or newer) but not
on i386,i486,i586.
If you compile for i486, it will run on i486, i586, i686 - but not on
i386.
Gabor> I want compile a libc that usable on every i4-686 processor, and also
Gabor> gcc, binutils. I must do this for every type of processor, or I can do
Gabor> it on a 486, without any feature missing?
Just compile for i486. You don't miss a feature - just maybe a tiny
bit of speed (but you should test yourself if you can measure this at
all).
Andreas
- --
Andreas Jaeger [EMAIL PROTECTED] [EMAIL PROTECTED]
for pgp-key finger [EMAIL PROTECTED]
------------------------------
End of linux-gcc-digest V1 #398
*******************************
To subscribe to linux-gcc-digest, send the command:
subscribe linux-gcc-digest
in the body of a message to "[EMAIL PROTECTED]". If you want
to subscribe something other than the account the mail is coming from,
such as a local redistribution list, then append that address to the
"subscribe" command; for example, to subscribe "local-linux-gcc":
subscribe linux-gcc-digest [EMAIL PROTECTED]
A non-digest (direct mail) version of this list is also available; to
subscribe to that instead, replace all instances of "linux-gcc-digest"
in the commands above with "linux-gcc".
