Upgrade gcc 2.7.0 to 2.7.2.1 and ld.so.1.9.5

Upgrade gcc 2.7.0 to 2.7.2.1 and ld.so.1.9.5

Post by Hans Bij » Thu, 14 Aug 1997 04:00:00



After upgrading from gcc 2.7.0 to gcc 2.7.2.1 and trying to install
ld.so.1.9.5, gcc does not work anymore.
Even a simple hello.c won't compile.
Error messages are something like:
/tmp/cc..........i: 1: numeric constants with no digits
..
/tmp/cc..........i: 7: invalid # line
..
                               : parse error at null character

The numeric constants error message and the invalid # line message are
repeated several times. The message is the parse error message and I
had to stop it by using Cntrl-C.

I am sure I made a mistake  when I installed the new packages, but I
don't know what I did wrong.

 
 
 

Upgrade gcc 2.7.0 to 2.7.2.1 and ld.so.1.9.5

Post by Andy For » Thu, 14 Aug 1997 04:00:00



> After upgrading from gcc 2.7.0 to gcc 2.7.2.1 and trying to install
> ld.so.1.9.5, gcc does not work anymore.
> Even a simple hello.c won't compile.
> Error messages are something like:
> /tmp/cc..........i: 1: numeric constants with no digits
> ..
> /tmp/cc..........i: 7: invalid # line
> ..
>                                : parse error at null character

> The numeric constants error message and the invalid # line message are
> repeated several times. The message is the parse error message and I
> had to stop it by using Cntrl-C.

> I am sure I made a mistake  when I installed the new packages, but I
> don't know what I did wrong.

  did you run ldconfig?

 
 
 

Upgrade gcc 2.7.0 to 2.7.2.1 and ld.so.1.9.5

Post by Andy For » Fri, 15 Aug 1997 04:00:00



> After upgrading from gcc 2.7.0 to gcc 2.7.2.1 and trying to install
> ld.so.1.9.5, gcc does not work anymore.
> Even a simple hello.c won't compile.
> Error messages are something like:
> /tmp/cc..........i: 1: numeric constants with no digits
> ..
> /tmp/cc..........i: 7: invalid # line
> ..
>                                : parse error at null character

> The numeric constants error message and the invalid # line message are
> repeated several times. The message is the parse error message and I
> had to stop it by using Cntrl-C.

> I am sure I made a mistake  when I installed the new packages, but I
> don't know what I did wrong.

  did you run ldconfig?
 
 
 

Upgrade gcc 2.7.0 to 2.7.2.1 and ld.so.1.9.5

Post by Hans Bij » Sun, 17 Aug 1997 04:00:00




>> After upgrading from gcc 2.7.0 to gcc 2.7.2.1 and trying to install
>> ld.so.1.9.5, gcc does not work anymore.
>> Even a simple hello.c won't compile.
>> Error messages are something like:
>> /tmp/cc..........i: 1: numeric constants with no digits
>> ..
>> /tmp/cc..........i: 7: invalid # line
>> ..
>>                                : parse error at null character

>> The numeric constants error message and the invalid # line message are
>> repeated several times. The message is the parse error message and I
>> had to stop it by using Cntrl-C.

>> I am sure I made a mistake  when I installed the new packages, but I
>> don't know what I did wrong.

>  did you run ldconfig?

Yes, this is automatically done when you run instldso.sh
But thanks very much. The problem is solved.

After experimenting with gcc, I was sure it was not ld.so
that caused the problem but the compiler.
Also it was not the preprocessor because gcc -E worked fine.
After some surfing at different websites, I decided to get
all the files I needed to upgrade in binary (!) format and had
to install libc-5.4.33 and binutils-2.8.1.0.1 in binary format
first.
So one has to install:
1) libc-5.4.17.bin.tar.gz
2) binutils-2.7.0.3.bin.tar.gz
3) gcc-2.7.2.1.bin.tar.gz

After installing these files, I had to install the latest
version of make (3.75), because the old make did not
correctly found the default Makefile in the current directory.

After installing these files I recompiled ld.so
(ld.so-1.8.5.tar.gz) with success.

After that installation of:
- modules-2.0.0
- iBCS-2.0.9.970513
- fvwm95-2.0.43a
were piece of cake :-)

 
 
 

1. Puzzled by upgrading libraries (libc.so, gcc, ld.so, binutils)

I'm getting crazy with Linux library version numbers!

I found an interesting looking VRML web browser
vrweb-1.0b3-mesa-Linux1.2.5 (see
http://hgiicm.tu-graz.ac.at:80/4AB5E062/Cvrweb), but when I try to run
it it complains that it needs libc.so.4.6.

I have libc.so.4.5.24 and gcc 2.5.8 and kernel 1.2.11 and ld.so 1.4.3.

I searched for a newer version of libc.so, and found libc-4.6.27, whose
release.libc-4.6.27 says I need to upgrade my gcc to 2.6.2. It also
warns about regex library. It also says I must upgrade my binutils.

I also looked at libc-4.7.2, but it seemed to require upgrading to gcc
2.7.0 and new binutils and even get libc-5.0.9 for some missing include
files!

So does this really mean that in order to run VRweb I have to upgrade
libc, gcc, ld.so and binutils?

I think I can manage without ELF for some time. And I have heard about
problems with gcc's newer than 2.5.8 (is it true that Linus still uses
2.5.8?), especially when compiling new kernels. So what is the absolute
minimum set of upgrades I have to do?

I'm really confused, could anybody write a simple UPGRADE-HOWTO? I find
the release.libc-*.*.* documents a bit confusing. And I'd like to hear
about the risks of upgrading too.
--

2. /etc/ptmp: Permission Denied.

3. Upgrading Gcc ..help with ld.so ...

4. control Value of variable within multi-scripts

5. GCC, libc, ld upgrade problems...

6. 2.5.1 to 7 upgrade issues?...

7. Chicken & egg thing: upgrading linux/gcc/binutils/libc/ld...

8. Long number in Tcsh/Csh

9. ld.so-1.9.5 upgrade ld.so segfault

10. Upgrade gcc 2.96-98 to gcc 3.2-7 on Redhat 7.2

11. gcc 2.7.2.1 upgrade problem, is this the latest gcc?

12. Want to upgrade from GCC 2.4.5 to GCC 2.5.8

13. Upgrading from GCC 1.40 to GCC 2.11c, problems