Skip to contentSkip to conversation

glibc-2.1.2 cross-compile problem

DISCUSSION Elizabeth Clarke 4 participants 7 messages Apr 20, 2000 – Apr 28, 2000

lore
Share & tools
lore
#0 lore raw

I'm having a problem compiling glibc-2.1.2 using the xppc cross-compilation toolset. I (believe I) have followed the instructions for patching glibc
and all seemed fine, but I get the following, any help much appriciated!:

/opt/xppc/bin/powerpc-linux-gcc ../sysdeps/unix/sysv/linux/poll.c -c -DNDEBUG=1 -DSOFT_FLOAT -O2 -Wall
-Winline -Wstrict-prototypes -Wwrite-strings -mcpu=860 -msoft-float
-fpic -I../include -I. -I.. -I../libio -I../sysdeps/powerpc/elf
-I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/powerpc -I../sysdeps/unix/sysv/linux/powerpc -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/powerpc -I../sysdeps/wordsize-32 -I../sysdeps/ieee754 -I../sysdeps/libm-ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem /opt/xppc/lib/gcc-lib/powerpc-linux/egcs-2.91.66/include -isystem /usr/local/amino/module3/linux/linux/include -D_LIBC_REENTRANT -include
../include/libc-symbols.h -DPIC -o poll.os
../sysdeps/unix/bsd/poll.c: In function `__emulate_poll':
In file included from ../sysdeps/unix/sysv/linux/poll.c:62:
../sysdeps/unix/bsd/poll.c:194: internal error--insn does not satisfy its constraints:
(insn 1390 183 187 (set (reg:SI 12 r12)

        (unspec[
                (symbol_ref:SI ("@max_fd_size.39"))
                (reg:SI 65 lr)
            ]  8)) 398 {*movsi_got_internal} (nil)
    (nil))

toplev.c:1367: Internal compiler error in function fatal_insn

Thanks
Beth

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#1 lore raw
Quoted 4 lines · Elizabeth Clarke

I'm having a problem compiling glibc-2.1.2 using the xppc cross-compilation toolset. I (believe I) have followed the instructions for patching glibc and all seemed fine, but I get the following, any help much appriciated!:

Are you running gcc-2.95.2?

Regards,
Graham

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#2 lore raw
Quoted 8 lines · Graham Stoney
Quoted 4 lines · Elizabeth Clarke

I'm having a problem compiling glibc-2.1.2 using the xppc cross-compilation toolset. I (believe I) have followed the instructions for patching glibc and all seemed fine, but I get the following, any help much appriciated!:

Are you running gcc-2.95.2?

I wasn't, but I grabbed it yesterday afternoon and been trying to compile it as per the instructions at
http://members.home.net/mmporter/linux/cross/ which I found in your FAQ. I grabbed and compiled the latest binutils okay. But.... can't get gcc to compile. It took a little pursuading before it would use the new binutils, and now complains about stdio.h being missing:

/usr/local/src/gcc-2.95.2/gcc/xgcc -B/usr/local/src/gcc-2.95.2/gcc/ -B/usr/local/powerpc-linux/bin/ -c -DHAVE_CONFIG_H -g -O2 -I. -I./../../include choose-temp.c
choose-temp.c:29: stdio.h: No such file or directory choose-temp.c:30: sys/types.h: No such file or directory choose-temp.c:32: unistd.h: No such file or directory choose-temp.c:35: stdlib.h: No such file or directory choose-temp.c:38: sys/file.h: No such file or directory make[2]: *** [choose-temp.o] Error 1
make[2]: Leaving directory `/usr/local/src/gcc-2.95.2/powerpc-linux/libiberty' make[1]: *** [all-target-libiberty] Error 2
make[1]: Leaving directory `/usr/local/src/gcc-2.95.2'

Aaaaaarrrrggggghhhhhhhhhhh!
Beth
feeling a little frustrated

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#3 lore raw

The cross-tools want to have the target system header files
available in a directory called "sys-include" underneath the target triplet in the installation directory. The target triplet directory wants to look like /usr on the real system and the gcc-fixed header files will go into the regular "include" directory.

David

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#4 lore raw
In reply to Elizabeth Clarke
Quoted 21 lines · Elizabeth Clarke
Quoted 8 lines · Graham Stoney
Quoted 4 lines · Elizabeth Clarke

I'm having a problem compiling glibc-2.1.2 using the xppc cross-compilation toolset. I (believe I) have followed the instructions for patching glibc and all seemed fine, but I get the following, any help much appriciated!:

Are you running gcc-2.95.2?

I wasn't, but I grabbed it yesterday afternoon and been trying to compile it as per the instructions at
http://members.home.net/mmporter/linux/cross/ which I found in your FAQ. I grabbed and compiled the latest binutils okay. But.... can't get gcc to compile. It took a little pursuading before it would use the new binutils, and now complains about stdio.h being missing:

/usr/local/src/gcc-2.95.2/gcc/xgcc -B/usr/local/src/gcc-2.95.2/gcc/

(quoted diff) +0 -2
-B/usr/local/powerpc-linux/bin/ -c -DHAVE_CONFIG_H -g -O2 -I.
-I./../../include  choose-temp.c
Quoted 1 line

choose-temp.c:29: stdio.h: No such file or directory

Are you sure you followed the directions on my site? You need to configure your build of gcc with "--with-newlib" then link to your kernel headers, then build glibc.

--
Matt Porter
[email protected]
This is Linux Country. On a quiet night, you can hear Windows reboot.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#5 lore raw
Quoted 8 lines · Matt Porter
Quoted 4 lines

/usr/local/src/gcc-2.95.2/gcc/xgcc -B/usr/local/src/gcc-2.95.2/gcc/

(quoted diff) +0 -2
-B/usr/local/powerpc-linux/bin/ -c -DHAVE_CONFIG_H -g -O2 -I.
-I./../../include  choose-temp.c

choose-temp.c:29: stdio.h: No such file or directory

Are you sure you followed the directions on my site? You need to configure your build of gcc with "--with-newlib" then link to your kernel headers, then build glibc.

Yes... after all they are not complex instructions.

I sorted that problem (stdio.h missing) by copying the newlib headers into /usr/local/powerpc-linux/include. So it gets past that now. But....

/usr/local/src/gcc-2.95.2/gcc/xgcc -B/usr/local/src/gcc-2.95.2/gcc/ -B/usr/local/powerpc-linux/bin/ -c -g -O2 -I. -I. -D_IO_MTSAFE_IO iogetline.c -o pic/iogetline.o /usr/local/src/gcc-2.95.2/gcc/xgcc -B/usr/local/src/gcc-2.95.2/gcc/ -B/usr/local/powerpc-linux/bin/ -c -g -O2 -I. -I. -D_IO_MTSAFE_IO iogetline.c
In file included from iolibio.h:1,

                 from libioP.h:47,
                 from iogetline.c:26:

libio.h:30: _G_config.h: No such file or directory make[1]: *** [iogetline.o] Error 1 make[1]: Leaving directory `/usr/local/src/gcc-2.95.2/powerpc-linux/libio'

So now I'm where Graham Stoney was at Date: Thu, 12 Aug 1999 14:34:44 -0400.
I *think* it is looking for _G_config.h from my host includes, but it simply isn't putting the path on the command line. Which I think it did at one point, or at least on of those -I. was -I./../../include. Arghh I'm must be going mad, or stupid. Surely its should not be as bad as this?

Any help very much appreciated!
Beth

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#6 lore raw

Hi Elizabeth,

Quoted 9 lines · Elizabeth Clarke

/usr/local/src/gcc-2.95.2/gcc/xgcc -B/usr/local/src/gcc-2.95.2/gcc/ -B/usr/local/powerpc-linux/bin/ -c -g -O2 -I. -I. -D_IO_MTSAFE_IO iogetline.c -o pic/iogetline.o /usr/local/src/gcc-2.95.2/gcc/xgcc -B/usr/local/src/gcc-2.95.2/gcc/ -B/usr/local/powerpc-linux/bin/ -c -g -O2 -I. -I. -D_IO_MTSAFE_IO iogetline.c
In file included from iolibio.h:1,

                 from libioP.h:47,
                 from iogetline.c:26:
Quoted 7 lines

libio.h:30: _G_config.h: No such file or directory make[1]: *** [iogetline.o] Error 1 make[1]: Leaving directory `/usr/local/src/gcc-2.95.2/powerpc-linux/libio'

So now I'm where Graham Stoney was at Date: Thu, 12 Aug 1999 14:34:44 -0400.

Can't remember what I did to solve this, but I got past it somehow. Try doing a "make install", and see if it installs enough of the compiler to go ahead with the glibc build. I found I had to build gcc in two passes, firstly with --with-newlib, and then without once glibc was installed.

Quoted 1 line

Surely its should not be as bad as this?

Agreed. Funnily enough though, it's better than it used to be. I remember when I was a lad, before "configure" was around...

Good luck,
Graham
--
Graham Stoney
Principal Hardware/Software Engineer
Canon Information Systems Research Australia
Ph: +61 2 9805 2909 Fax: +61 2 9805 2929

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/