Re: 3.0.4 cross build fails on i686-pc-cygwin.

Re: 3.0.4 cross build fails on i686-pc-cygwin.

[Mack Lobell]

How do i do that?

The last time i built a cross compiler i didn't have to add anything to the 
build process.
I have read a few how-tos on how to build a cross compiler and none of them 
give any examples, so i appreciate any help i can get.

I'm planing to use newlib instead of glibc. But to build newlib i need a 
cross compiler, right?

Regards.


>From: David Edelsohn <dje@watson.ibm.com>
>To: "Mack Lobell" <macklobell@hotmail.com>
>CC: gcc@gcc.gnu.org
>Subject: Re: 3.0.4 cross build fails on i686-pc-cygwin.
>Date: Fri, 22 Feb 2002 12:52:09 -0500
>
>	You need to supply the cross-target headers and tell GCC where to
>find them.  This can be glibc or libgloss or your own, but it needs to be
>something.
>
>David


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

RE: 3.0.4 cross build fails on i686-pc-cygwin.

[Stephano Mariani]

Get to a powerpc system, and copy the headers and libraries.

Stephano Mariani

> -----Original Message-----
> From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] On Behalf
Of Mack Lobell
> Sent: Friday, 22 February 2002 6 34
> To: dje@watson.ibm.com
> Cc: gcc@gcc.gnu.org
> Subject: Re: 3.0.4 cross build fails on i686-pc-cygwin.
> 
> How do i do that?
> 
> The last time i built a cross compiler i didn't have to add anything
to the
> build process.
> I have read a few how-tos on how to build a cross compiler and none of
them
> give any examples, so i appreciate any help i can get.
> 
> I'm planing to use newlib instead of glibc. But to build newlib i need
a
> cross compiler, right?
> 
> Regards.
> 
> 
> >From: David Edelsohn <dje@watson.ibm.com>
> >To: "Mack Lobell" <macklobell@hotmail.com>
> >CC: gcc@gcc.gnu.org
> >Subject: Re: 3.0.4 cross build fails on i686-pc-cygwin.
> >Date: Fri, 22 Feb 2002 12:52:09 -0500
> >
> >	You need to supply the cross-target headers and tell GCC where
to
> >find them.  This can be glibc or libgloss or your own, but it needs
to be
> >something.
> >
> >David
> 
> 
> _________________________________________________________________
> Chat with friends online, try MSN Messenger: http://messenger.msn.com

RE: 3.0.4 cross build fails on i686-pc-cygwin.

[Mack Lobell]

Hi,

i finally succeeded in building a cross compiler, but i don't think i did it 
right.

My first approach was to add the flag --with-headers=/some 
path/newlib/libc/include. These file were then copied to 
prefix/powerpc-eabi/sys-include and used in some parts of the builing. The 
build still failes on i686-pc-cygwin and i386-unknown-freebsd4.5 with this 
approach. After looking around some more i found that make looks in 
prefix/powerpc-eabi/include NOT in sys-include?? If i copy sys-include to 
include the build succeeds on i686-pc-cygwin but not on 
i386-unknown-freebsd4.5.

My second approach was to copy newlib/libc/include to srcdir, with this 
approach the build succeeds on i686-pc-cygwin (i haven't tryied it on 
FreeBSD yet).

If any of these approaches are right please let me know.

When i look through the make.log i find several "implicit declaration" 
warnings so i still think i screwed up the path's:
../../../../gcc-3.0.4/libiberty/strdup.c: In function `strdup':
../../../../gcc-3.0.4/libiberty/strdup.c:5: warning: implicit declaration of 
function `malloc'
../../../../gcc-3.0.4/libiberty/strdup.c:5: warning: implicit declaration of 
function `strlen'
../../../../gcc-3.0.4/libiberty/strdup.c:8: warning: implicit declaration of 
function `strcpy'

I would really appreciate if someone could give an example on how to 
configure and make a cross compiler using newlib.

Regards.


>From: Jan Reimers <janr@molienergy.com>
>To: 'Mack Lobell' <macklobell@hotmail.com>, dje@watson.ibm.com
>CC: gcc@gcc.gnu.org
>Subject: RE: 3.0.4 cross build fails on i686-pc-cygwin.
>Date: Fri, 22 Feb 2002 12:15:44 -0800
>
>Tell gcc where the newlib headers are, build cross-gcc, then use cross-gcc
>to make the lib.
>
>
> > -----Original Message-----
> > From: Mack Lobell [mailto:macklobell@hotmail.com]
> > Sent: Friday, February 22, 2002 10:34 AM
> > To: dje@watson.ibm.com
> > Cc: gcc@gcc.gnu.org
> > Subject: Re: 3.0.4 cross build fails on i686-pc-cygwin.
> >
> >
> > How do i do that?
> >
> > The last time i built a cross compiler i didn't have to add
> > anything to the
> > build process.
> > I have read a few how-tos on how to build a cross compiler
> > and none of them
> > give any examples, so i appreciate any help i can get.
> >
> > I'm planing to use newlib instead of glibc. But to build
> > newlib i need a
> > cross compiler, right?
> >
> > Regards.
> >
> >
> > >From: David Edelsohn <dje@watson.ibm.com>
> > >To: "Mack Lobell" <macklobell@hotmail.com>
> > >CC: gcc@gcc.gnu.org
> > >Subject: Re: 3.0.4 cross build fails on i686-pc-cygwin.
> > >Date: Fri, 22 Feb 2002 12:52:09 -0500
> > >
> > >	You need to supply the cross-target headers and tell
> > GCC where to
> > >find them.  This can be glibc or libgloss or your own, but
> > it needs to be
> > >something.
> > >
> > >David
> >
> >
> > _________________________________________________________________
> > Chat with friends online, try MSN Messenger: http://messenger.msn.com
> >


_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

RE: 3.0.4 cross build fails on i686-pc-cygwin.

[Jan Reimers]

Tell gcc where the newlib headers are, build cross-gcc, then use cross-gcc
to make the lib.


> -----Original Message-----
> From: Mack Lobell [mailto:macklobell@hotmail.com]
> Sent: Friday, February 22, 2002 10:34 AM
> To: dje@watson.ibm.com
> Cc: gcc@gcc.gnu.org
> Subject: Re: 3.0.4 cross build fails on i686-pc-cygwin.
> 
> 
> How do i do that?
> 
> The last time i built a cross compiler i didn't have to add 
> anything to the 
> build process.
> I have read a few how-tos on how to build a cross compiler 
> and none of them 
> give any examples, so i appreciate any help i can get.
> 
> I'm planing to use newlib instead of glibc. But to build 
> newlib i need a 
> cross compiler, right?
> 
> Regards.
> 
> 
> >From: David Edelsohn <dje@watson.ibm.com>
> >To: "Mack Lobell" <macklobell@hotmail.com>
> >CC: gcc@gcc.gnu.org
> >Subject: Re: 3.0.4 cross build fails on i686-pc-cygwin.
> >Date: Fri, 22 Feb 2002 12:52:09 -0500
> >
> >	You need to supply the cross-target headers and tell 
> GCC where to
> >find them.  This can be glibc or libgloss or your own, but 
> it needs to be
> >something.
> >
> >David
> 
> 
> _________________________________________________________________
> Chat with friends online, try MSN Messenger: http://messenger.msn.com
> 

Re: 3.0.4 cross build fails on i686-pc-cygwin.

[David Edelsohn]

	You need to supply the cross-target headers and tell GCC where to
find them.  This can be glibc or libgloss or your own, but it needs to be
something. 

David

RE: 3.0.4 cross build fails on i686-pc-cygwin.

[Stephano Mariani]

You need the includes and libraries for the target.

Stephano Mariani

> -----Original Message-----
> From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] On Behalf
Of Mack Lobell
> Sent: Friday, 22 February 2002 5 42
> To: gcc@gcc.gnu.org
> Subject: 3.0.4 cross build fails on i686-pc-cygwin.
> 
> Hi,
> 
> i'm trying to build a 3.0.4 cross compiler for powerpc target.
Binutils is
> installed in /usr/local/powerpc and compiled for powerpc-eabi.
> 
> The build was configured the following way:
> $ gcc --version
> 2.95.3-5
> $ target=powerpc-eabi
> $ host=i686-pc-cygwin
> $ build=i686-pc-cygwin
> $ prefix=/usr/local/powerpc
> $../../gcc-3.0.4/configure --enable-languages=c,c++
--with-included-gettext
> --enable-shared --enable-threads --target=$target --with-newlib
> --prefix=$prefix --with-ld=/usr/local/powerpc/bin/powerpc-eabi-ld.exe
> --with-as=/usr/local/powerpc/bin/powerpc-eabi-as.exe --host=$host
> --build=$build -v > cross_conf.log 2>&1
> $ make CFLAGS="-v -save-temps" > cross_make.log 2>&1
> 
> The build fails when trying to compile libiberty/argv.c.
> 
> make[1]: Entering directory
`/home/guest/build/gcc/powerpc-eabi/libiberty'
> if [ x"-fPIC" != x ] && [ ! -d pic ]; then \
>   mkdir pic; \
> else true; fi
> touch stamp-picdir
> CONFIG_FILES= CONFIG_HEADERS=config.h:config.in /bin/sh
./config.status
> creating config.h
> config.h is unchanged
> if [ x"-fPIC" != x ]; then \
>   /home/guest/build/gcc/gcc/xgcc -B/home/guest/build/gcc/gcc/
-nostdinc
> -B/home/guest/build/gcc/powerpc-eabi/newlib/ -isystem
> /home/guest/build/gcc/powerpc-eabi/newlib/targ-include -isystem
> /home/guest/gcc-3.0.4/newlib/libc/include
> -B/usr/local/powerpc/powerpc-eabi/bin/
> -B/usr/local/powerpc/powerpc-eabi/lib/ -isystem
> /usr/local/powerpc/powerpc-eabi/include -c -DHAVE_CONFIG_H -v
-save-temps
> -I. -I../../../../gcc-3.0.4/libiberty/../include  -W -Wall
-Wtraditional
> -pedantic -fPIC ../../../../gcc-3.0.4/libiberty/argv.c -o pic/argv.o;
\
> else true; fi
> Reading specs from /home/guest/build/gcc/gcc/specs
> Configured with: ../../gcc-3.0.4/configure --enable-languages=c,c++
> --with-included-gettext --enable-shared --enable-threads
> --target=powerpc-eabi --with-newlib --prefix=/usr/local/powerpc
> --with-ld=/usr/local/powerpc/bin/powerpc-eabi-ld.exe
> --with-as=/usr/local/powerpc/bin/powerpc-eabi-as.exe
--host=i686-pc-cygwin
> --build=i686-pc-cygwin -v
> Thread model: single
> gcc version 3.0.4
> /home/guest/build/gcc/gcc/cpp0.exe -lang-c -nostdinc -v -I.
> -I../../../../gcc-3.0.4/libiberty/../include -iprefix
> /home/guest/build/gcc/gcc/../lib/gcc-lib/powerpc-eabi/3.0.4/ -isystem
> /home/guest/build/gcc/gcc/include -isystem
> /home/guest/build/gcc/powerpc-eabi/newlib/include -isystem
> /usr/local/powerpc/powerpc-eabi/bin/include -isystem
> /usr/local/powerpc/powerpc-eabi/lib/include -D__GNUC__=3
-D__GNUC_MINOR__=0
> -D__GNUC_PATCHLEVEL__=4 -DPPC -D__embedded__ -D__PPC__ -D__embedded__
> -D__PPC -Asystem=embedded -Acpu=powerpc -Amachine=powerpc
> -D__CHAR_UNSIGNED__ -D__NO_INLINE__ -D__STDC_HOSTED__=1 -W -Wall
> -Wtraditional -pedantic -D__PIC__=2 -D__pic__=2 -D_CALL_SYSV
-D_BIG_ENDIAN
> -D__BIG_ENDIAN__ -Amachine=bigendian -D_ARCH_PPC -DHAVE_CONFIG_H
-isystem
> /home/guest/build/gcc/powerpc-eabi/newlib/targ-include -isystem
> /home/guest/gcc-3.0.4/newlib/libc/include -isystem
> /usr/local/powerpc/powerpc-eabi/include
> ../../../../gcc-3.0.4/libiberty/argv.c argv.i
> ignoring nonexistent directory
> "/home/guest/build/gcc/powerpc-eabi/newlib/include"
> ignoring nonexistent directory
"/usr/local/powerpc/powerpc-eabi/bin/include"
> ignoring nonexistent directory
"/usr/local/powerpc/powerpc-eabi/lib/include"
> ignoring nonexistent directory
> "/home/guest/build/gcc/powerpc-eabi/newlib/targ-include"
> ignoring nonexistent directory
"/home/guest/gcc-3.0.4/newlib/libc/include"
> ignoring nonexistent directory
"/usr/local/powerpc/powerpc-eabi/include"
> GNU CPP version 3.0.4 (cpplib) (PowerPC Embedded)
> #include "..." search starts here:
> #include <...> search starts here:
> .
> ../../../../gcc-3.0.4/include
> /home/guest/build/gcc/gcc/include
> End of search list.
> ../../../../gcc-3.0.4/libiberty/argv.c:35:20: string.h: No such file
or
> directory
> ../../../../gcc-3.0.4/libiberty/argv.c:36:20: stdlib.h: No such file
or
> directory
> make[1]: *** [argv.o] Error 1
> make[1]: Leaving directory
`/home/guest/build/gcc/powerpc-eabi/libiberty'
> make: *** [all-target-libiberty] Error 2
> 
> 
> If needed i have the logs from make and configure, and i have the
> preprocessed files.
> 
> I have the same problem trying to build a 3.0.3 cross. Is this is bug
or is
> it me?
> 
> Regards.
> 
> _________________________________________________________________
> Send and receive Hotmail on your mobile device: http://mobile.msn.com

3.0.4 cross build fails on i686-pc-cygwin.

[Mack Lobell]

Hi,

i'm trying to build a 3.0.4 cross compiler for powerpc target. Binutils is 
installed in /usr/local/powerpc and compiled for powerpc-eabi.

The build was configured the following way:
$ gcc --version
2.95.3-5
$ target=powerpc-eabi
$ host=i686-pc-cygwin
$ build=i686-pc-cygwin
$ prefix=/usr/local/powerpc
$../../gcc-3.0.4/configure --enable-languages=c,c++ --with-included-gettext 
--enable-shared --enable-threads --target=$target --with-newlib 
--prefix=$prefix --with-ld=/usr/local/powerpc/bin/powerpc-eabi-ld.exe 
--with-as=/usr/local/powerpc/bin/powerpc-eabi-as.exe --host=$host 
--build=$build -v > cross_conf.log 2>&1
$ make CFLAGS="-v -save-temps" > cross_make.log 2>&1

The build fails when trying to compile libiberty/argv.c.

make[1]: Entering directory `/home/guest/build/gcc/powerpc-eabi/libiberty'
if [ x"-fPIC" != x ] && [ ! -d pic ]; then \
  mkdir pic; \
else true; fi
touch stamp-picdir
CONFIG_FILES= CONFIG_HEADERS=config.h:config.in /bin/sh ./config.status
creating config.h
config.h is unchanged
if [ x"-fPIC" != x ]; then \
  /home/guest/build/gcc/gcc/xgcc -B/home/guest/build/gcc/gcc/ -nostdinc 
-B/home/guest/build/gcc/powerpc-eabi/newlib/ -isystem 
/home/guest/build/gcc/powerpc-eabi/newlib/targ-include -isystem 
/home/guest/gcc-3.0.4/newlib/libc/include 
-B/usr/local/powerpc/powerpc-eabi/bin/ 
-B/usr/local/powerpc/powerpc-eabi/lib/ -isystem 
/usr/local/powerpc/powerpc-eabi/include -c -DHAVE_CONFIG_H -v -save-temps 
-I. -I../../../../gcc-3.0.4/libiberty/../include  -W -Wall -Wtraditional 
-pedantic -fPIC ../../../../gcc-3.0.4/libiberty/argv.c -o pic/argv.o; \
else true; fi
Reading specs from /home/guest/build/gcc/gcc/specs
Configured with: ../../gcc-3.0.4/configure --enable-languages=c,c++ 
--with-included-gettext --enable-shared --enable-threads 
--target=powerpc-eabi --with-newlib --prefix=/usr/local/powerpc 
--with-ld=/usr/local/powerpc/bin/powerpc-eabi-ld.exe 
--with-as=/usr/local/powerpc/bin/powerpc-eabi-as.exe --host=i686-pc-cygwin 
--build=i686-pc-cygwin -v
Thread model: single
gcc version 3.0.4
/home/guest/build/gcc/gcc/cpp0.exe -lang-c -nostdinc -v -I. 
-I../../../../gcc-3.0.4/libiberty/../include -iprefix 
/home/guest/build/gcc/gcc/../lib/gcc-lib/powerpc-eabi/3.0.4/ -isystem 
/home/guest/build/gcc/gcc/include -isystem 
/home/guest/build/gcc/powerpc-eabi/newlib/include -isystem 
/usr/local/powerpc/powerpc-eabi/bin/include -isystem 
/usr/local/powerpc/powerpc-eabi/lib/include -D__GNUC__=3 -D__GNUC_MINOR__=0 
-D__GNUC_PATCHLEVEL__=4 -DPPC -D__embedded__ -D__PPC__ -D__embedded__ 
-D__PPC -Asystem=embedded -Acpu=powerpc -Amachine=powerpc 
-D__CHAR_UNSIGNED__ -D__NO_INLINE__ -D__STDC_HOSTED__=1 -W -Wall 
-Wtraditional -pedantic -D__PIC__=2 -D__pic__=2 -D_CALL_SYSV -D_BIG_ENDIAN 
-D__BIG_ENDIAN__ -Amachine=bigendian -D_ARCH_PPC -DHAVE_CONFIG_H -isystem 
/home/guest/build/gcc/powerpc-eabi/newlib/targ-include -isystem 
/home/guest/gcc-3.0.4/newlib/libc/include -isystem 
/usr/local/powerpc/powerpc-eabi/include 
../../../../gcc-3.0.4/libiberty/argv.c argv.i
ignoring nonexistent directory 
"/home/guest/build/gcc/powerpc-eabi/newlib/include"
ignoring nonexistent directory "/usr/local/powerpc/powerpc-eabi/bin/include"
ignoring nonexistent directory "/usr/local/powerpc/powerpc-eabi/lib/include"
ignoring nonexistent directory 
"/home/guest/build/gcc/powerpc-eabi/newlib/targ-include"
ignoring nonexistent directory "/home/guest/gcc-3.0.4/newlib/libc/include"
ignoring nonexistent directory "/usr/local/powerpc/powerpc-eabi/include"
GNU CPP version 3.0.4 (cpplib) (PowerPC Embedded)
#include "..." search starts here:
#include <...> search starts here:
.
../../../../gcc-3.0.4/include
/home/guest/build/gcc/gcc/include
End of search list.
../../../../gcc-3.0.4/libiberty/argv.c:35:20: string.h: No such file or 
directory
../../../../gcc-3.0.4/libiberty/argv.c:36:20: stdlib.h: No such file or 
directory
make[1]: *** [argv.o] Error 1
make[1]: Leaving directory `/home/guest/build/gcc/powerpc-eabi/libiberty'
make: *** [all-target-libiberty] Error 2


If needed i have the logs from make and configure, and i have the 
preprocessed files.

I have the same problem trying to build a 3.0.3 cross. Is this is bug or is 
it me?

Regards.

_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com