linux-gcc-digest Monday, 11 October 1999 Volume 01 : Number 399
In this issue:
Loading and starting of linux ELF executables.
Re: Loading and starting of linux ELF executables.
binutils bug with m68k jump instr
binutils 2.9.5.0.12 is released.
accessing a structure inside a structure
Re: accessing a structure inside a structure
Re: accessing a structure inside a structure
accessing a structure inside a structure
$9.95 wholesale website hosting
binutils 2.9.5.0.13 is released.
Upgrading glibc.
Re: Upgrading glibc.
Re: Upgrading glibc.
Re: Upgrading glibc.
Re: Upgrading glibc.
binutils 2.9.5.0.14 is released.
Re: Upgrading glibc.
Re: Upgrading glibc.
gcc-2.95.1 and configure
Re: gcc-2.95.1 and configure
RE: gcc-2.95.1 and configure
Re: gcc-2.95.1 and configure
Makefile problem
Re: Makefile problem
gcc installation
gdb 4.17.0.14 is released.
Re: gdb 4.17.0.14 is released.
gcc installation
Latest version...
Re: gcc installation
Re: Latest version...
Date: Wed, 6 Oct 1999 09:31:34 +0400
question about using glibc2.0 and glic2.1 at the same time
libtcp
GDB 4.18-5 is released (RPM package of 19991004 snapshot)
Re: GDB 4.18-5 is released (RPM package of 19991004 snapshot)
Re: GDB 4.18-5 is released (RPM package of 19991004 snapshot)
Someone help a newbie?
Re: question about using glibc2.0 and glic2.1 at the same time
Re: libtcp
Re: Someone help a newbie?
Re: question about using glibc2.0 and glic2.1 at the same time
See the end of the digest for information on subscribing to the linux-gcc
or linux-gcc-digest mailing lists.
----------------------------------------------------------------------
From: Lokesh Setia <[EMAIL PROTECTED]>
Date: Thu, 9 Sep 1999 11:04:19 +0530 (IST)
Subject: Loading and starting of linux ELF executables.
[please CC: to [EMAIL PROTECTED] as i'm not a member - thanks]
Hi,
I want to know how an executable loads up, what all is initialized before
the control is passed onto main() function, and all this stuff. In
particular:
1. What's the role of crt0.o crtn.o etc. ??
2. How are the arguments and environment variables passed?
3. What all initializations/static variables are made by glibc, and how do
I control these?
I don't need an exact binary specification of these things, just the
concept, with some detail.
Any pointers will be helpful (and please cc: a reply!).
With warm regards,
Lokesh Setia.
,-, %~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| =======
___oo | "Lately it occurs to me, | -----
//_ooo | what a looooong strange trip its been." | ----
,-----'o ~ooo | | --
?o-----o__ooo--`======___________________________________======___= ~~~~~~~~
`-(*)--===~~~~~~(*)(*)o (*)(*)o --------
- -------------------------------------------------------------------------------
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Lokesh Setia o "The crystal ship is being filled, o
o #include <sys/disclaimer.h> o a thousand girls, a thousand thrills, o
o Hughes Software Systems. o a million ways to spend your time, when o
o To: <[EMAIL PROTECTED]> o we get back, i'll drop a line." o
o Cc: <[EMAIL PROTECTED]> o -------------> The Doors o
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
------------------------------
From: "Rus V. Brushkoff" <[EMAIL PROTECTED]>
Date: Thu, 9 Sep 1999 11:46:50 +0300 (EET DST)
Subject: Re: Loading and starting of linux ELF executables.
On Thu, 9 Sep 1999, Lokesh Setia wrote:
:
:
: [please CC: to [EMAIL PROTECTED] as i'm not a member - thanks]
:
: Hi,
:
: I want to know how an executable loads up, what all is initialized before
: the control is passed onto main() function, and all this stuff. In
: particular:
:
: 1. What's the role of crt0.o crtn.o etc. ??
: 2. How are the arguments and environment variables passed?
: 3. What all initializations/static variables are made by glibc, and how do
: I control these?
:
: I don't need an exact binary specification of these things, just the
: concept, with some detail.
:
: Any pointers will be helpful (and please cc: a reply!).
:
Some of them at :
http://lightning.voshod.com/asm/startup.html
others in gcc/glibc sources.
:
:
Rus
------------------------------
From: Roman Zippel <[EMAIL PROTECTED]>
Date: Thu, 9 Sep 1999 20:28:18 +0200 (MET DST)
Subject: binutils bug with m68k jump instr
Hi,
I'm using a linux-i386 -> linux-m68k crosscompiler setup and found a
problem with binutils-2.9.5.0.7. The following example should show
the problem:
.global abc,def
start:
bras abc
.rept 64
nop
.endr
abc:
nop
bras def
nop
def:
nop
The assembler doesn't complain about the first illegal jump, but about the
second legal one. If I remove the .global line it works.
There is a second (maybe related) problem. The assemble doesn't optimize
anymore short jumps to global labels. The following source produces two
different jump instructions:
.global abc
jra abc
nop
abc: jra def
nop
def:
Both problems are not binutils 2.9.1.
bye, Roman
------------------------------
From: [EMAIL PROTECTED] (H.J. Lu)
Date: Fri, 10 Sep 1999 16:06:16 -0700 (PDT)
Subject: binutils 2.9.5.0.12 is released.
This is the beta release of binutils 2.9.5.0.12 for Linux, which is
based on binutils 1999 0910 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.12 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.11:
1. Update from binutils 1999 0910. It fixed a PIC linker bug on ix86
and sparc introduced in the last release.
2. i370 update.
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.12.tar.gz. Source code.
2. binutils-2.9.5.0.11-2.9.5.0.12.diff.gz. Patch against the previous
beta source code.
3. binutils-2.9.5.0.12-1.src.rpm. Source RPM.
4. binutils-2.9.5.0.12-1.i386.rpm. X86 inary RPM for RedHat 6.0.
5. binutils-2.9.5.0.12-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/10/99
------------------------------
From: Raju K V <[EMAIL PROTECTED]>
Date: Wed, 15 Sep 1999 13:22:56 +0530
Subject: accessing a structure inside a structure
hi all,
I have 2 structure of as follows:
struct a
{
int x;
void *y;
};
struct b
{
char *u;
int v;
float z;
};
and in my code I write as
main()
{
struct a a1;
struct b b1;
.
.
b1.u = "hello";
b1.v = 10;
b1.z = 20.1;
.
.
a1.y = (struct b *)&b1;
.
.
fun(&a1);
.
.
}
fun(struct a *x1)
{
struct b y1;
.
.
y1 = (struct b *)x1;
printf("%s\n",y1.u);
.
.
}
what I want to know is that is it possible to access the struct b
component in struct a without using the temperory variable y1?
Thanks and regards,
Raju
------------------------------
From: Kurt Wall <[EMAIL PROTECTED]>
Date: Wed, 15 Sep 1999 02:27:26 -0600
Subject: Re: accessing a structure inside a structure
Also sprach Raju K V:
> hi all,
>
> I have 2 structure of as follows:
>
> struct a
> {
> int x;
> void *y;
> };
>
> struct b
> {
> char *u;
> int v;
> float z;
> };
So far so good.
> and in my code I write as
>
> main()
> {
> struct a a1;
> struct b b1;
> .
> .
> b1.u = "hello";
Boom! You've just caused a SIGSEV because you're assigning memory
that you haven't allocated properly. b1.u could point anywhere.
malloc and family are your friends.
> b1.v = 10;
> b1.z = 20.1;
> .
> .
> a1.y = (struct b *)&b1;
Nope, that dog won't hunt. everything after your first invalid memory
reference creates undefined, probably fatal, behavior.
Kurt
- --
COBOL is for morons.
-- E.W. Dijkstra
------------------------------
From: Przemek Borys <[EMAIL PROTECTED]>
Date: Wed, 15 Sep 1999 12:46:45 +0200
Subject: Re: accessing a structure inside a structure
EHLO Kurt!
>> main()
>> {
>> struct a a1;
>> struct b b1;
>> .
>> .
>> b1.u = "hello";
> Boom! You've just caused a SIGSEV because you're assigning memory
> that you haven't allocated properly. b1.u could point anywhere.
> malloc and family are your friends.
b1 is not a pointer, and referencing to it's internal object u is
valid. = "hello" only changes the value of the pointer u.
- --
____\___\___
(_(\|,|_|,|_ Gassho! [http://dione.ids.pl/~pborys][mr MUA home]
| | |. [teksty o zen,programowaniu,moje sf,xfaq_pl, inne]
------------------------------
From: Przemek Borys <[EMAIL PROTECTED]>
Date: Wed, 15 Sep 1999 12:44:45 +0200
Subject: accessing a structure inside a structure
EHLO Raju!
> struct a
> {
> int x;
> void *y;
> };
> struct b
> {
> char *u;
> int v;
> float z;
> };
> y1 = (struct b *)x1;
probably y1 = *((struct b*)x1->y) ?
> printf("%s\n",y1.u);
> what I want to know is that is it possible to access the struct b
> component in struct a without using the temperory variable y1?
((struct b *)x1->y)->u
- --
____\___\___
(_(\|,|_|,|_ Gassho! [http://dione.ids.pl/~pborys][mr MUA home]
| | |. [teksty o zen,programowaniu,moje sf,xfaq_pl, inne]
------------------------------
From: [EMAIL PROTECTED]
Date: Sat, 18 Sep 1999 17:22:09 -0500
Subject: $9.95 wholesale website hosting
We offer Web Hosting for the following server platform: NT 4.0 Running IIS4
as low as $9.95/month, paid quarterly or annually, plus a $19.95 set-up fee
All our servers are Dell Poweredge dual PIII 4300 series
Our Connectivity is based on redundant state of the art equiptment
*** Call Now!!! for details 888-848-HOST(4678) ***
Our $9.95/mo. hosting includes:
FREE!!! Registration of a domain or transfer
100mb Storage
Bandwith Unlimited
FrontPage 2000 extensions FREE!!!
Unlimited e-mail accounts
Unlimited Autoresponders
Full Control E-mail Administration
24 hour private FTP access ftp.yourdomain.com
Your own Cgi-Bin Directory
Daily tape back-ups
UPS Backups
30 Day money back guarantee
Same day set-up
24 hour access and monitoring of your site
Access Logs
Additional features (some additional charges)
ODBC Support
Cold Fusion Support
ASP Support
Secure Server (SSL) access
Real Audio/Video
**Call for details 888-848-HOST(4678)**
------------------------------
From: [EMAIL PROTECTED] (H.J. Lu)
Date: Wed, 22 Sep 1999 18:05:02 -0700 (PDT)
Subject: binutils 2.9.5.0.13 is released.
This is the beta release of binutils 2.9.5.0.13 for Linux, which is
based on binutils 1999 0922 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.13 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.12:
1. Update from binutils 1999 0922.
2. i370 update.
Changes from binutils 2.9.5.0.11:
1. Update from binutils 1999 0910. It fixed a PIC linker bug on ix86
and sparc introduced in the last release.
2. i370 update.
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.13.tar.bz2. Source code.
2. binutils-2.9.5.0.12-2.9.5.0.13.diff.bz2. Patch against the previous
beta source code.
3. binutils-2.9.5.0.13-1.src.rpm. Source RPM.
4. binutils-2.9.5.0.13-1.i386.rpm. X86 inary RPM for RedHat 6.0.
5. binutils-2.9.5.0.13-1.alpha.rpm. Alpha binary RPM for RedHat 6.0.
There are no gz 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/220/99
------------------------------
From: Tim Hillman <[EMAIL PROTECTED]>
Date: Mon, 27 Sep 1999 08:43:40 -0700 (PDT)
Subject: Upgrading glibc.
Is there A HOWTO or web site that discusses upgrading one version of glibc
to another ? The only ones I can find deal with moving from libc5 to libc6
which I have already done successfully.
I am currently running glibc-2.0.7pre6 on debian 2.1. I obtained the
sources to glibc-2.1.2, compiled ok with gcc-2.95.1, I then did make
install to /lib and /usr/lib.
At that point, I thought the proper thing to do was to move the symlinks
from the old libraries to the new ones (and the ld-linux.so.2 link to the
new loader).
Kaboom!
None of my existing binaries work. They all complain of the same
undefined symbol (It escapes me at the moment, but I will re-create it and
get the exact name if I didn't go about this the wrong way).
Is 2.0.7 binary compatible with 2.1.2 ?
Tim Hillman
------------------------------
From: "Davide Libenzi" <[EMAIL PROTECTED]>
Date: Mon, 27 Sep 1999 18:03:16 +0200
Subject: Re: Upgrading glibc.
Hi Tim,
You _must_ use Debian packages for glibc or patch original sources with the
patch supplied by Debian.
Cheers,
Davide.
- --
"Debian, the Freedom in Freedom."
------------------------------
From: Keith Duthie <[EMAIL PROTECTED]>
Date: Tue, 28 Sep 1999 04:22:14 +1200 (NZST)
Subject: Re: Upgrading glibc.
On Mon, 27 Sep 1999, Tim Hillman wrote:
> None of my existing binaries work. They all complain of the same
> undefined symbol (It escapes me at the moment, but I will re-create it and
> get the exact name if I didn't go about this the wrong way).
Would it be something along the lines of "__register_frame_info"? If so,
the problem is related to the c compiler. If you compile glibc with egcs
1.1.2, that problem will probably go away. OTOH, if you ask nicely on the
[EMAIL PROTECTED] you may be able to get a patch for this. IIRC, it's not a
bug, it's a feature.
> Is 2.0.7 binary compatible with 2.1.2 ?
The answer is yes and no. AFAICT most problems are to do with developers
using internal glibc symbols[1]. You might find it worthwhile to use the
glibc-compat addon, though.
[1] I'm a little hazy on this, but WTH.
- --
Understanding is a three edged sword. Do you *want* to get the point?
http://www.albatross.co.nz/~psycho/ O-
------------------------------
From: Andreas Jaeger <[EMAIL PROTECTED]>
Date: 27 Sep 1999 18:18:55 +0200
Subject: Re: Upgrading glibc.
>>>>> Tim Hillman writes:
Tim> Is there A HOWTO or web site that discusses upgrading one version of glibc
Tim> to another ? The only ones I can find deal with moving from libc5 to libc6
Tim> which I have already done successfully.
Tim> I am currently running glibc-2.0.7pre6 on debian 2.1. I obtained the
Tim> sources to glibc-2.1.2, compiled ok with gcc-2.95.1, I then did make
Tim> install to /lib and /usr/lib.
Tim> At that point, I thought the proper thing to do was to move the symlinks
Tim> from the old libraries to the new ones (and the ld-linux.so.2 link to the
Tim> new loader).
What are you doing? If you configure with --prefix=/usr, glibc should
create the correct symlinks for you.
Tim> Kaboom!
Tim> None of my existing binaries work. They all complain of the same
Tim> undefined symbol (It escapes me at the moment, but I will re-create it and
Tim> get the exact name if I didn't go about this the wrong way).
Please read the FAQ first. Most problems are documented there.
Tim> Is 2.0.7 binary compatible with 2.1.2 ?
Programs (not all libraries) which don't use the internal symbols of
glibc and were compiled against glibc 2.0.7, should work with 2.1.2.
You might need to recompile some libraries as documented in the FAQ.
Andreas
- --
Andreas Jaeger [EMAIL PROTECTED] [EMAIL PROTECTED]
for pgp-key finger [EMAIL PROTECTED]
------------------------------
From: Andreas Jaeger <[EMAIL PROTECTED]>
Date: 27 Sep 1999 18:55:47 +0200
Subject: Re: Upgrading glibc.
>>>>> Davide Libenzi writes:
> Hi Tim,
> You _must_ use Debian packages for glibc or patch original sources with the
> patch supplied by Debian.
I agree that a Debian package is better integrated in a Debian system
- - but using the released glibc 2.1.2 for a Debian system should work.
Otherwise the Debian developers have done IMO something totally wrong.
Andreas
- --
Andreas Jaeger [EMAIL PROTECTED] [EMAIL PROTECTED]
for pgp-key finger [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (H.J. Lu)
Date: Mon, 27 Sep 1999 13:32:34 -0700 (PDT)
Subject: binutils 2.9.5.0.14 is released.
This is the beta release of binutils 2.9.5.0.14 for Linux, which is
based on binutils 1999 0925 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.14 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.13:
1. Update from binutils 1999 0925.
2. Fix a -s and linker script bug.
Changes from binutils 2.9.5.0.12:
1. Update from binutils 1999 0922.
2. i370 update.
Changes from binutils 2.9.5.0.11:
1. Update from binutils 1999 0910. It fixed a PIC linker bug on ix86
and sparc introduced in the last release.
2. i370 update.
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.14.tar.bz2. Source code.
2. binutils-2.9.5.0.13-2.9.5.0.14.diff.bz2. Patch against the previous
beta source code.
3. binutils-2.9.5.0.14-1.src.rpm. Source RPM.
4. binutils-2.9.5.0.14-1.i386.rpm. X86 inary RPM for RedHat 6.0.
5. binutils-2.9.5.0.14-1.alpha.rpm. Alpha binary RPM for RedHat 6.0.
There are no gz 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/25/99
------------------------------
From: Wolfram Gloger <[EMAIL PROTECTED]>
Date: 28 Sep 1999 07:48:15 -0000
Subject: Re: Upgrading glibc.
> >>>>> Davide Libenzi writes:
>
> > Hi Tim,
> > You _must_ use Debian packages for glibc or patch original sources with the
> > patch supplied by Debian.
>
> I agree that a Debian package is better integrated in a Debian system
> - but using the released glibc 2.1.2 for a Debian system should work.
> Otherwise the Debian developers have done IMO something totally wrong.
I absolutely agree with Andreas here -- could you explain _why_ a
special Debian patch for glibc is critically necessary ? And why
wasn't it posted/discussed on the glibc mailing lists ?
I really like Debian but my home machine is completely
distribution-neutral (everything compiled from source) and I _need_ to
be able to compile packages on that machine and then count on the fact
that they run on a recent Debian release... Until now, this worked
reasonably OK.
Regards,
Wolfram.
- --
`Surf the sea, not double-u three...'
[EMAIL PROTECTED]
------------------------------
From: "Davide Libenzi" <[EMAIL PROTECTED]>
Date: Tue, 28 Sep 1999 10:41:15 +0200
Subject: Re: Upgrading glibc.
Hi,
I've tried to install glibc from sources time ago and it fails.
Someone told me that it wasn't possible to do that without previously patch
the sources
with Debian patch.
I've not seen the patch but so I can't say enough about it.
It was 8 months ago, and I don't know if now it's possible.
I agree with the fact that it must be possible to install for sources,
anyway I continue
to like Debian.
Cheers,
Davide.
- --
"Debian, the Freedom in Freedom."
------------------------------
From: Tim Hillman <[EMAIL PROTECTED]>
Date: Wed, 29 Sep 1999 07:34:35 -0700 (PDT)
Subject: gcc-2.95.1 and configure
After apparently screwing up an upgrade to glibc-2.1.2, I decided to
completely wipe my system and start "fresh" (This is my "play" machine, so
that's ok).
On a fresh debian 2.1 ftp install (basic development environment), I have:
gcc-2.7.2.3
egcs-1.1.1
binutils 2.9.1.0.19
glibc-2.0.7
a newly installed 2.2.12 kernel and source.
When I run configure for gcc-2.95.1, it insists on building the compiler
for a i586-pc-linux-gnulibc1 system. However, /usr/include/features.h
clearly has __GLIBC__ 2 and minor of 0. When I try to force it with
configure --prefix=/usr --host=i586-pc-linux-gnu , it says that it can't
find the glibc minor number.
Also, if I try to continue as gnulibc1, the build quits after about five
minutes with an 'internal compiler error, fatal signal 11'.
Incidentally, I can't build egcs-1.1.2 either, same problem.
I see in the faq that comes with the source, there is a reference to
Signal 11 on Linux, but there is no entry for it. Only a reference to a
file on a server someplace that I can't seem to get to. I think it is out
of date.
Tim Hillman
------------------------------
From: Keith Duthie <[EMAIL PROTECTED]>
Date: Thu, 30 Sep 1999 03:41:28 +1200 (NZST)
Subject: Re: gcc-2.95.1 and configure
On Wed, 29 Sep 1999, Tim Hillman wrote:
> I see in the faq that comes with the source, there is a reference to
> Signal 11 on Linux, but there is no entry for it. Only a reference to a
> file on a server someplace that I can't seem to get to. I think it is out
> of date.
Your problem is either not enough virtual memory, or (more likely) bad
hardware. Look at http://www.bitwizard.nl/sig11/ for more details.
- --
Understanding is a three edged sword. Do you *want* to get the point?
http://www.albatross.co.nz/~psycho/ O-
------------------------------
From: "Michael A. Traffanstead" <[EMAIL PROTECTED]>
Date: Wed, 29 Sep 1999 10:55:37 -0500
Subject: RE: gcc-2.95.1 and configure
> > I see in the faq that comes with the source, there is a reference to
> > Signal 11 on Linux, but there is no entry for it. Only a reference
to a
> > file on a server someplace that I can't seem to get to. I think it
is out
> > of date.
> Your problem is either not enough virtual memory, or (more likely) bad
> hardware. Look at http://www.bitwizard.nl/sig11/ for more details.
Overclocking and/or overheating can also cause this... forget running
quake for stability testing, just recompile the linux kernel a few times.
:*)
traff
------------------------------
From: Tim Hillman <[EMAIL PROTECTED]>
Date: Wed, 29 Sep 1999 12:37:31 -0700 (PDT)
Subject: Re: gcc-2.95.1 and configure
Well, I would come to the hardware conclusion too if it were not for two
things:
1) I can compile the kernel (2.2.12) all day long with no problems.
2) I had a working system and compiled gcc-2.95.1 with egcs-1.1.2 and
glibc-2.1.2 with the the resulting gcc ( I only had a problem when I
botched the install of the resulting library and ended up --long story--
re-installing the base debian 2.1 system etc... etc...).
3) I had the same problem on another machine running slackware 3.0 that I
upgraded by hand to glibc-2.0.7. There was some kind of funny interaction
between the supplied gcc-2.7.2.3 and gcc-2.8.1 that I was trying to build.
I ended up downgrading to gcc-2.7.2.1 and then gcc-2.8.1 would build.
Then, I could build egcs-1.1.2 and then glibc-2.0.7. I still don't know
why gcc-2.7.2.1 would build gcc-2.8.1, but 2.7.2.3 would not.
If nobody has any insight for me, I guess I will have to go through this
time consuming, "step up through compiler versions" process again.
I also am wondering why configure can't seem to determine the right minor
number for the installed glibc.
Sorry to bother you folks with this, but it's frustrating to say the least
:)
Tim Hillman
On Thu, 30 Sep 1999, Keith Duthie wrote:
> On Wed, 29 Sep 1999, Tim Hillman wrote:
>
> > I see in the faq that comes with the source, there is a reference to
> > Signal 11 on Linux, but there is no entry for it. Only a reference to a
> > file on a server someplace that I can't seem to get to. I think it is out
> > of date.
> Your problem is either not enough virtual memory, or (more likely) bad
> hardware. Look at http://www.bitwizard.nl/sig11/ for more details.
>
> --
> Understanding is a three edged sword. Do you *want* to get the point?
> http://www.albatross.co.nz/~psycho/ O-
>
>
------------------------------
From: "Mark Spitz-Nagel" <[EMAIL PROTECTED]>
Date: Thu, 30 Sep 1999 10:10:24 -0700
Subject: Makefile problem
I can't seem to figure out why a certain C program won't compile under linux with this
Makefile. It compiles fine under Unix (Sun). Do I need to change this Makefile in any
way for it to work under Linux (RH5.2)? I tried removing the colons from ":=", but to
no avail. Any suggestions would be most appreciated.
Thanks,
Mark
Makefile:
OBJ:=main.o myalloc.o choleski.o
PROG:=demo1
CPPFLAGS:= -I.
CFLAGS:= -g
default: $(PROG)
$(OBJ) : %.o : %.c
gcc -o $@ $(CPPFLAGS) $(CFLAGS) -c $^
$(PROG): $(OBJ)
gcc -o $@ $^ -lm -lc
HotBot - Search smarter.
http://www.hotbot.com
------------------------------
From: Keith Duthie <[EMAIL PROTECTED]>
Date: Fri, 1 Oct 1999 16:56:51 +1200 (NZST)
Subject: Re: Makefile problem
On Thu, 30 Sep 1999, Mark Spitz-Nagel wrote:
> I can't seem to figure out why a certain C program won't compile under
> linux with this Makefile. It compiles fine under Unix (Sun). Do I need
> to change this Makefile in any way for it to work under Linux (RH5.2)? I
> tried removing the colons from ":=", but to no avail. Any suggestions
> would be most appreciated.
<snip>
> $(OBJ) : %.o : %.c
I believe the above is your problem. Try removing the "$(OBJ) : ".
- --
Understanding is a three edged sword. Do you *want* to get the point?
http://www.albatross.co.nz/~psycho/ O-
------------------------------
From: Chris Wan <[EMAIL PROTECTED]>
Date: Sat, 02 Jan 1999 04:06:36 -0800
Subject: gcc installation
Hello, i'm trying to install gcc on to a IBM powerpc aix 4.3.2.0. however,
i'm getting the following errors after configuring the compiler for
installation:
id: 0711-317 ERROR: Undefined symbol: .alloca
id: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
information
make: 1254-004 The error code from the last command is 8.
Stop.
make: 1254-004 The error code from the last command is 2.
Stop.
make: 1254-004 The error code from the last command is 8.
How do i solve this problem?
Thankx,
Chris
______________________________
Chris Wan Direct line 604 207-6416
MDSI Mobile Data Solutions Telephone 604 207-6000
10271 Shellbridge Way Facsimile 604 207-6060
Richmond, BC Email [EMAIL PROTECTED]
Canada, V6X 2W8 www.mdsi-advantex.com
------------------------------
From: [EMAIL PROTECTED] (H.J. Lu)
Date: Sun, 3 Oct 1999 12:28:18 -0700 (PDT)
Subject: gdb 4.17.0.14 is released.
Hi, Folks,
This is the beta release of gdb 4.17.0.14, which is based on gdb 4.17
plus Linux/x86 hardware watchpoint/FPU, glibc 2 pthread and Linux/PPC
support. You need linux 2.0.35 or above, or 2.1.xx to get the x86 FPU
to work correctly. The Linux/x86 binary works with all recent kernels
and C libraries, and the x86 FPU support is enabled at the run-time,
depending on the kernel version.
You need the latest glibc 2.1.1 to debug LinuxThreads.
Special thanks to Dan Bethe who provided the PowePC notebook which
makes the LinuxPPC support in gdb possible.
Please report any bugs related to gdb 4.17.0.14 to [EMAIL PROTECTED]
Problems:
Because most of system calls in glibc 2 are written in assembly without
frame pointer, gdb may not be able to debug nor get stack trace system
calls on glibc-based 2 systems. Due to this, "make check" may fail in
FAIL: gdb.base/a1-selftest.exp: backtrace through signal handler
FAIL: gdb.base/signals.exp: bt in signals.exp
with glibc 2.
Also, it is normal to see
FAIL: gdb.base/interrupt.exp: continue (timeout)
FAIL: gdb.base/interrupt.exp: echo data (timeout)
if there is
XPASS: gdb.base/interrupt.exp: send_gdb end of file
Due to the new cplus-dem.c from gcc 2.95.1, you will get a few
FAIL: gdb.c++/demangle.exp: maint demangle __xxxxxxxxxx
Changes from gdb 4.17.0.13:
1. Fixed a thread/signal race condition.
2. Fixed a dead thread bug.
3. Added AMD Athlon support in disassembler.
Changes from gdb 4.17.0.12:
1. Update cplus-dem.c from gcc 2.95.1.
Changes from gdb 4.17.0.11:
1. Support LinuxThreads on PowerPC.
2. Support P/III and AMD 3DNow! instructions.
3. Fix debugging dynamically loaded shared object.
Changes from gdb 4.17.0.10:
1. Support glibc 2.0 and libc 5.
2. Support LinuxThreads on alpha.
3. Support Solaris 2.7/x86.
Changes from gdb 4.17.0.9:
1. Fix support for glibc 2.1 pthread. Need the latest glibc 2.1, newer
than 16:30pm PST of 19990-02-03.
2. Fix deleting the hardware watchpoint on x86.
Changes from gdb 4.17.0.8:
1. The new cplus-dem.c from egcs 1999-01-12 with a bug fix.
2. Add support for deleting the hardware watchpoint on x86.
3. Update support for glibc 2.1 pthread.
4. Fix C++ testsuite.
Changes from gdb 4.17.0.6:
1. Support for glibc 2.1 pthread. But it doesn't work, probably due
to the CLONE_PTRACE change to pthread in glibc 2.1.
2. Add support for the older Linux C libraries.
3. Add -static support for glibc 2.1.
Changes from gdb 4.17.0.5:
1. Support for glibc 2.0 pthread. It doesn't work with glibc 2.1.
2. The Linux/PPC support.
3. The Linux/Sparc support. Untested.
Changes from gdb 4.17.0.4:
1. Fix the Intel FPU tag code handling.
Changes from gdb 4.17.0.3:
1. Fix testcases for FPU.
2. Fix x86 hardware watchpoint support.
Changes from gdb 4.17.0.2:
1. Fake FP registers on older kernels.
Changes from gdb 4.17:
1. Linux/x86 FPU support is added. You can debug floating point numbers
just like integers.
2. x86 hardware watchpoint is extended to long long, double and long
double.
3. More information on x86 CPU status register.
4. Fix a bug when reading beyond the memory boundary.
The file list:
1. gdb-4.17-4.17.0.14.diff.gz. Patch against gdb 4.17.
2. gdb-4.17.0.13-4.17.0.14.diff.gz. Patch against gdb 4.17.0.13.
3. gdb-4.17.0.14.x86.gz. Precompiled Linux/x86 statically linked binary.
The ftp sites for my gdb patches:
ftp://ftp.valinux.com/pub/support/hjl/gdb
gdb 4.17 source code is available at
ftp://ftp.gnu.org/pub/gnu
To install the precompiled binary,
# gunzp gdb-4.17.0.14.x86.gz
# cp gdb-4.17.0.14.x86 /usr/bin/gdb
H.J.
[EMAIL PROTECTED]
10/03/1999
------------------------------
From: Alex Buell <[EMAIL PROTECTED]>
Date: Sun, 3 Oct 1999 23:08:38 +0100 (BST)
Subject: Re: gdb 4.17.0.14 is released.
On Sun, 3 Oct 1999, H.J. Lu wrote:
> This is the beta release of gdb 4.17.0.14, which is based on gdb 4.17
> plus Linux/x86 hardware watchpoint/FPU, glibc 2 pthread and Linux/PPC
> support. You need linux 2.0.35 or above, or 2.1.xx to get the x86 FPU
> to work correctly. The Linux/x86 binary works with all recent kernels
> and C libraries, and the x86 FPU support is enabled at the run-time,
> depending on the kernel version.
Just why are you are causing a code fork between your version of gdb and
GNU's 4.18 version of gdb?
Cheers,
Alex
- --
Legalise cannabis today! Got PGP? Ask me for public key.
http://www.tahallah.demon.co.uk - updated!
------------------------------
From: "Chris Wong" <[EMAIL PROTECTED]>
Date: Tue, 05 Oct 1999 15:28:44 PDT
Subject: gcc installation
Hello,
I'm trying to install gcc onto a IBM powerpc running AIX 4.3.0 (not 100%
sure on the version). I'm getting the following errors and don't know how
to fix it. Any suggestions??
Thankx,
Chris
________________-
cc -DIN_GCC -DHAIFA -O2 -g -DHAVE_CONFIG_H -Wl,-bbigtoc -o
genattr genattr.o rtl.o bitmap.o print-rtl.o ` case "obstack.o" in ?*) echo
obstack.o ;; esac ` ` case "alloca.o" in ?*) echo alloca.o ;; esac ` ` case
"" in ?*) echo ;; esac ` ` case "" in ?*) echo ;; esac ` ` case "" in
?*) echo ;; esac ` -lld
ld: 0711-317 ERROR: Undefined symbol: .alloca
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
information.
make: 1254-004 The error code from the last command is 8.
Stop.
make: 1254-004 The error code from the last command is 2.
Stop.
make: 1254-004 The error code from the last command is 2.
Stop.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
------------------------------
From: "William Scott Lockwood III" <[EMAIL PROTECTED]>
Date: Tue, 5 Oct 1999 18:27:57 -0500
Subject: Latest version...
Hello all!
Where can I get the latest version of GCC? Thanks.
Scott
------------------------------
From: [EMAIL PROTECTED]
Date: Tue, 5 Oct 1999 22:53:31 -0500 (CDT)
Subject: Re: gcc installation
It's been rumoured that Chris Wong said:
>
> Hello,
>
> I'm trying to install gcc onto a IBM powerpc running AIX 4.3.0 (not 100%
> sure on the version). I'm getting the following errors and don't know how
> to fix it. Any suggestions??
>
> cc -DIN_GCC -DHAIFA -O2 -g -DHAVE_CONFIG_H -Wl,-bbigtoc -o
> genattr genattr.o rtl.o bitmap.o print-rtl.o ` case "obstack.o" in ?*) echo
> obstack.o ;; esac ` ` case "alloca.o" in ?*) echo alloca.o ;; esac ` ` case
> "" in ?*) echo ;; esac ` ` case "" in ?*) echo ;; esac ` ` case "" in
> ?*) echo ;; esac ` -lld
> ld: 0711-317 ERROR: Undefined symbol: .alloca
I assume you are using xlc to compile gcc.
You need to
export CC="cc -ma -qcpluscmt"
>>>>>>before<<<<<<
you run configure
------------------------------
From: "Ernesto Caballero" <[EMAIL PROTECTED]>
Date: Wed, 6 Oct 1999 09:23:02 +0400
Subject: Re: Latest version...
try http://www.gnu.org/software/gcc/gcc.html
- ----- Original Message -----
From: William Scott Lockwood III <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 06, 1999 3:27 AM
Subject: Latest version...
> Hello all!
> Where can I get the latest version of GCC? Thanks.
>
> Scott
>
------------------------------
From: "Ernesto Caballero" <[EMAIL PROTECTED]>
Date: Wed, 6 Oct 1999 09:31:34 +0400
Subject: Date: Wed, 6 Oct 1999 09:31:34 +0400
This is a multi-part message in MIME format.
- ------=_NextPart_000_00C7_01BF0FDD.94C9B7A0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
hello there:
I have a question for you. I dont know is it te rigth place but anyway.
I have installed RedHat Linux 6.0 and glibc 2.1.
The problem is that i have too Interbase 4.0 for linux. The libraries =
for=20
interbase were linked against glibc2.0 from REdHat 5.1.
I have installed the compat-* rpm from the installation. How can I link =
my programs to the interbase that uses glibc2.0. and how can i tell to =
the loader to use=20
glibc2.1 or glibc2.0 at the same time depending on the library the =
current program need.
Thans in advance
Ernesto
- ------=_NextPart_000_00C7_01BF0FDD.94C9B7A0
Content-Type: text/html;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dkoi8-r" http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3401" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3D"Arial Cyr" size=3D2>hello there:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>I have a question for you. I dont =
know is it=20
te rigth place but anyway.</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>I have installed RedHat Linux 6.0 =
and glibc=20
2.1.</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>The problem is that i have too =
Interbase 4.0=20
for linux. The libraries for </FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>interbase were linked against =
glibc2.0 from=20
REdHat 5.1.</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>I have installed the compat-* rpm =
from the=20
installation. How can I link my programs to the interbase that uses =
</FONT><FONT=20
face=3D"Arial Cyr" size=3D2>glibc2.0. and how can i tell to the =
loader to use=20
</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>glibc2.1 or glibc2.0 at the same =
time=20
depending on the library the current program need.</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2> =
=20
Thans in=20
advance</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2> =
=20
=
=20
=
=20
=
=20
Ernesto</FONT></DIV></BODY></HTML>
- ------=_NextPart_000_00C7_01BF0FDD.94C9B7A0--
------------------------------
From: "Ernesto Caballero" <[EMAIL PROTECTED]>
Date: Wed, 6 Oct 1999 09:54:17 +0400
Subject: question about using glibc2.0 and glic2.1 at the same time
This is a multi-part message in MIME format.
- ------=_NextPart_000_00D6_01BF0FE0.C0FD9B40
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
hello there:
I have a question for you. I dont know is it te rigth place but anyway.
I have installed RedHat Linux 6.0 and glibc 2.1.
The problem is that i have too Interbase 4.0 for linux. The libraries =
for=20
interbase were linked against glibc2.0 from REdHat 5.1.
I have installed the compat-* rpm from the installation. How can I link =
my programs to the interbase that uses glibc2.0. and how can i tell to =
the loader to use=20
glibc2.1 or glibc2.0 at the same time depending on the library the =
current program need.
Thans in advance
Ernesto
- ------=_NextPart_000_00D6_01BF0FE0.C0FD9B40
Content-Type: text/html;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dkoi8-r" http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3401" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3D"Arial Cyr" size=3D2>
<DIV><FONT face=3D"Arial Cyr" size=3D2>hello there:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>I have a question for you. I dont =
know is it=20
te rigth place but anyway.</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>I have installed RedHat Linux 6.0 =
and glibc=20
2.1.</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>The problem is that i have too =
Interbase 4.0=20
for linux. The libraries for </FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>interbase were linked against =
glibc2.0 from=20
REdHat 5.1.</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>I have installed the compat-* rpm =
from the=20
installation. How can I link my programs to the interbase that uses =
</FONT><FONT=20
face=3D"Arial Cyr" size=3D2>glibc2.0. and how can i tell to the =
loader to use=20
</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2>glibc2.1 or glibc2.0 at the same =
time=20
depending on the library the current program need.</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2> =
=20
Thans in=20
advance</FONT></DIV>
<DIV><FONT face=3D"Arial Cyr" size=3D2> =
=20
=
=20
=
=20
=
=20
Ernesto</FONT></DIV></FONT></DIV></BODY></HTML>
- ------=_NextPart_000_00D6_01BF0FE0.C0FD9B40--
------------------------------
From: "Gabor Z. Papp" <[EMAIL PROTECTED]>
Date: Wed, 6 Oct 1999 12:09:17 +0200
Subject: libtcp
I'm not a programmer, but I would like compile this library
under linux 2.2.12 glibc 2.1.2 with gcc-2.95.1
The error:
g++ -O2 -c tcp_server.c
tcp_server.c: In method `void TcpServer::run_server()':
tcp_server.c:136: passing `int *' as argument 3 of `accept(int, sockaddr *, socklen_t
*)' changes signedness
tcp_server.c: In method `int TcpServer::access_allowed(int)':
tcp_server.c:188: passing `int *' as argument 3 of `getpeername(int, sockaddr *,
socklen_t *)' changes signedness
tcp_server.c: In method `char * TcpServer::get_peer_addr(int)':
tcp_server.c:208: passing `int *' as argument 3 of `getpeername(int, sockaddr *,
socklen_t *)' changes signedness
make: *** [tcp_server.o] Error 1
How can I fix this? Please be detailed, thanks.
------------------------------
From: Jim Kingdon <[EMAIL PROTECTED]>
Date: Thu, 7 Oct 1999 18:14:42 -0400
Subject: GDB 4.18-5 is released (RPM package of 19991004 snapshot)
This release, for Linux, includes:
* threads
* floating point fixes
* a fix regarding backtraces through signal handlers
* many C++ fixes (compared with GDB 4.18)
probably some other stuff I'm forgetting. For those who have been
following GDB development, this is nothing new, it is the 19991004
snapshot, very lightly patched. But it my hope that putting it into
an RPM package will lead to more people testing it.
Get x86 and source RPM packages at http://people.redhat.com/kingdon/
Report bugs at http://developer.redhat.com/bugzilla/ (you can put in
"rawhide" for the release as this package will be in the next weekly
rawhide release) and/or http://sourceware.cygnus.com/gdb/ (take your
pick).
------------------------------
From: Stan Shebs <[EMAIL PROTECTED]>
Date: Thu, 7 Oct 1999 16:03:49 -0700
Subject: Re: GDB 4.18-5 is released (RPM package of 19991004 snapshot)
Date: Thu, 7 Oct 1999 18:14:42 -0400
From: Jim Kingdon <[EMAIL PROTECTED]>
This release, for Linux, includes:
* threads
* floating point fixes
* a fix regarding backtraces through signal handlers
* many C++ fixes (compared with GDB 4.18)
probably some other stuff I'm forgetting. For those who have been
following GDB development, this is nothing new, it is the 19991004
snapshot, very lightly patched. But it my hope that putting it into
an RPM package will lead to more people testing it.
This is a great idea, thanks very much!
Get x86 and source RPM packages at http://people.redhat.com/kingdon/
Report bugs at http://developer.redhat.com/bugzilla/ (you can put in
"rawhide" for the release as this package will be in the next weekly
rawhide release) and/or http://sourceware.cygnus.com/gdb/ (take your
pick).
Presumably you mean the mailing lists referenced on the .../gdb/ page.
Stan
------------------------------
From: Jim Kingdon <[EMAIL PROTECTED]>
Date: Thu, 7 Oct 1999 23:03:31 -0400
Subject: Re: GDB 4.18-5 is released (RPM package of 19991004 snapshot)
> This is a great idea, thanks very much!
Yeah, well, it was a demangling bug in 4.18
(http://developer.redhat.com/bugzilla/show_bug.cgi?id=4835) which
pushed me over the edge. gdb-4.18-5 should be a big step forward for
C++ debugging (as far as I know), but I'm still looking for people to
find and report bugs. In particular, I'm aware of cases in which
spurious SIGTRAP's happen and pretty much make debugging impossible
(thread-related, I would guess, but I don't really know, I might know
how to reproduce some of these but I'm not sure).
There is now a gdb-4.18-6.*.rpm on http://people.redhat.com/kingdon/ -
the only difference from -5 is fixing a small but annoying problem
with the info files.
> Presumably you mean the mailing lists referenced on the .../gdb/ page.
If people can't figure that out, do we really want bug reports from
them? :-)
Seriously, yeah, it would have been good to be a bit more explicit.
------------------------------
From: "William Scott Lockwood III" <[EMAIL PROTECTED]>
Date: Sat, 9 Oct 1999 18:31:13 -0500
Subject: Someone help a newbie?
Okay, I admit it: GCC is smarter than I am, because even after reading the
DOCS, I STILL can't get 2.95.1 to install. Could someone post a list of
commands to type, in order? I can configure it, and build it, I just can't
seem to get it to install and get the system using it. HELP!
A confused newbie,
Scott
------------------------------
From: "Martin v. Loewis" <[EMAIL PROTECTED]>
Date: Mon, 11 Oct 1999 08:52:13 +0200
Subject: Re: question about using glibc2.0 and glic2.1 at the same time
> The problem is that i have too Interbase 4.0 for linux. The
> libraries for interbase were linked against glibc2.0 from REdHat
> 5.1. I have installed the compat-* rpm from the installation. How
> can I link my programs to the interbase that uses glibc2.0. and how
> can i tell to the loader to use glibc2.1 or glibc2.0 at the same
> time depending on the library the current program need.
In theory, programs linked with glibc 2.0 should continue to work with
glibc 2.1, with no problems. So there is no need to link with glibc
2.0. Also, it is not possible.
Is there a problem with using glibc 2.1?
Regards,
Martin
------------------------------
From: "Martin v. Loewis" <[EMAIL PROTECTED]>
Date: Mon, 11 Oct 1999 08:49:44 +0200
Subject: Re: libtcp
> tcp_server.c:136: passing `int *' as argument 3 of `accept(int, sockaddr *,
>socklen_t *)' changes signedness
[...]
> How can I fix this? Please be detailed, thanks.
You must change the way the function "accept" is called in line 136 of
the file tcp_server.c. The parameter should be an address of a
variable of type "socklen_t", not an address of a variable of type
"int".
Hope this helps,
Martin
------------------------------
From: "Martin v. Loewis" <[EMAIL PROTECTED]>
Date: Mon, 11 Oct 1999 08:45:34 +0200
Subject: Re: Someone help a newbie?
> Okay, I admit it: GCC is smarter than I am, because even after reading the
> DOCS, I STILL can't get 2.95.1 to install. Could someone post a list of
> commands to type, in order? I can configure it, and build it, I just can't
> seem to get it to install and get the system using it.
Perhaps you could have posted the commands you have been executing, in
order, so that others can see what you've been doing wrong.
Also, I'm not sure what you mean by "get the system using it". The
"system" is not using gcc on its own; it is always the user who is
invoking gcc.
Anyway, the following sequence should do
tar xzvf gcc-...
cd gcc-2.95
mkdir obj
cd obj
../configure --prefix=/usr --enable-shared --enable-threads
make bootstrap
make install
Hope this helps,
Martin
------------------------------
From: Bernhard Heidegger <[EMAIL PROTECTED]>
Date: Mon, 11 Oct 1999 11:16:04 +0200 (CEST)
Subject: Re: question about using glibc2.0 and glic2.1 at the same time
>>>>> "|" == Martin v Loewis <[EMAIL PROTECTED]> writes:
>> The problem is that i have too Interbase 4.0 for linux. The
>> libraries for interbase were linked against glibc2.0 from REdHat
>> 5.1. I have installed the compat-* rpm from the installation. How
>> can I link my programs to the interbase that uses glibc2.0. and how
>> can i tell to the loader to use glibc2.1 or glibc2.0 at the same
>> time depending on the library the current program need.
|> In theory, programs linked with glibc 2.0 should continue to work with
|> glibc 2.1, with no problems. So there is no need to link with glibc
|> 2.0. Also, it is not possible.
|> Is there a problem with using glibc 2.1?
Yes, the following simple (C++) test program doesn't work under
glibc-2.1 if compiled/linked with glibc-2.0 (tested with RedHat 5.2
vs. RedHat 6.0)
- ---------------------------- snip --------------------------
#include <strstream.h>
main() {
char x ;
istrstream beitl (&x, 1) ;
char y ;
beitl.read (&y, 1) ;
}
- ---------------------------- snip --------------------------
Bernhard
get my pgp key from a public keyserver (keyID=0x62446355)
- -----------------------------------------------------------------------------
Bernhard Heidegger [EMAIL PROTECTED]
Hyperwave Software Research & Development
Albrechtgasse 9/2, A-8010 Graz
Voice: ++43/316/820918-25 Fax: ++43/316/820918-99
- -----------------------------------------------------------------------------
------------------------------
End of linux-gcc-digest V1 #399
*******************************
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".
