/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/include/asm causing errors...

/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/include/asm causing errors...

Post by Remco van den Be » Wed, 26 Jan 2000 04:00:00



I tried to compile the cddafs software from gracjan and it didn't compile
on my Linux machine at work but it did compile on my Linux machine at home.

After a while I figured out what the differences where of those two sytems.
The file:

  /usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/include/asm/posix_types.h

caused the errors.

This file is different from the one in:

  /usr/include/asm/posix_types.h

where asm is a link to:

  /usr/include/asm -> /usr/src/linux/include/asm

On my system at home, where I run egcs-2.91.60 the directory

  /usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.60/include/asm  

does NOT exist. That's why the software did compile on that machine
without any problems.

So I removed the directory /usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/include/asm
and now it also compiles on my machine at work.

But I still have some questions:

- Why is this asm directory duplicated by the installation of a compiler?
- If it is needed, how could it be that it is causing errors?

Thanks for any information about this....

-Remco

 
 
 

/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/include/asm causing errors...

Post by Paul Kimo » Wed, 26 Jan 2000 04:00:00




Quote:> I tried to compile the cddafs software from gracjan and it didn't compile
> on my Linux machine at work but it did compile on my Linux machine at home.

> After a while I figured out what the differences where of those two sytems.
> The file:
>  /usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/include/asm/posix_types.h
> caused the errors.

> This file is different from the one in:
>  /usr/include/asm/posix_types.h
> where asm is a link to:

>  /usr/include/asm -> /usr/src/linux/include/asm
> On my system at home, where I run egcs-2.91.60 the directory
>  /usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.60/include/asm  
> does NOT exist. That's why the software did compile on that machine
> without any problems.

> So I removed the directory /usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/include/asm
> and now it also compiles on my machine at work.

> But I still have some questions:

> - Why is this asm directory duplicated by the installation of a compiler?

Perhaps gcc doesn't like something in it, so it builds a fixed version for
its own use.

Quote:> - If it is needed, how could it be that it is causing errors?

It may have based its fixed version on an old asm/posix_types.h, i.e., one
that came with an older kernel than the one you wanted to work with.

--


 
 
 

1. /usr/lib/gcc-lib/i386-linux and /usr/lib/gcc-lib/i486-linux

Hi Linuxers,

I just got a new copy of gcc-2.4.5 and source code of the pl11.
After having done the installation of gcc-2.4.5, I realised that
I have an extra directory: /usr/lib/gcc-lib/i386-linux.
The question is whether I need to keep the old gcc stuff under
the i386-linux.  I really like to clean it up so as to save 5.1
meg disk space (another poor Linux user  ;-( ).

Your answer is very appreciated.  Please send answer directly
to my address or the corresponding interest parties to reduce
the network load.  Thank you in advance.

Wing



2. setfacl: What's wrong with this?

3. automake causing linker to look in /usr/lib/.libs for file

4. Gnu tar from SGI to Linux

5. Tell "configure" to use /usr/local/lib/sparcv9/ instead of /usr/local/lib/

6. RealPlayer for Redhat 7.1

7. One more time: /usr/include/linux, /usr/include/asm

8. ncsa referer directive

9. /usr/openwin/lib/libtt.so vs /usr/dt/lib/libtt.so (and ttsession) ?

10. linking /usr/local/lib/* to /usr/lib/

11. /usr/X386/lib/X11 <-> /usr/lib/X11

12. GCC doesn't like /usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1

13. how to /usr/openwin/lib/config/site.def up for gcc