Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Matej Kupljen <matej.kupljen@ultra.si>
To: kernel coder <lhrkernelcoder@gmail.com>
Cc: James E Wilson <wilson@specifix.com>, linux-mips@linux-mips.org
Subject: Re: gcc-4.1.0 cross-compile for MIPS
Date: Mon, 19 Jun 2006 09:19:13 +0200	[thread overview]
Message-ID: <1150701553.7203.9.camel@localhost.localdomain> (raw)
In-Reply-To: <f69849430606182340t72ed5a68l95a724ea933faf12@mail.gmail.com>

Hi,

See this thread:
http://sourceware.org/ml/crossgcc/2005-07/msg00030.html

BR,,
Matej


> yes you were right.When i did
> make all-gcc
> 
> It just compiled smoothly.
> 
> Now to compile glibc-2.3.6 ,I issued following sequence of commands
> 
> ../glibc-2.3.6/configure --host=mipsel-linux --prefix="/usr"
> --enable-add-ons --with-headers=/home/shahzad/install/mipsel/include
> 
>  make cross-compiling=yes
> install_root=/home/shahzad/install/mipsel/include  prefix=""
> install-headers
> 
> But following error was generated
> 
> make[1]: Entering directory `/home/shahzad/glibc-2.3.6' { echo
> '#include "posix/bits/posix1_lim.h"';            \   echo '#define
> _LIBC 1';                                       \   echo '#include
> "misc/sys/uio.h"'; } |                 \ gcc -mabi=32 -E -dM -MD -MP
> -MF /home/shahzad/build-glibc-headers/bits/stdio_lim.dT -MT
> '/home/shahzad/build-glibc-headers/bits/stdio_lim.h
> /home/shahzad/build-glibc-headers/bits/stdio_lim.d'      \
>       -Iinclude -I. -I/home/shahzad/build-glibc-headers  -Ilibio
> -Inptl -I/home/shahzad/build-glibc-headers -Isysdeps/mips/elf
> -Inptl/sysdeps/unix/sysv/linux -Inptl/sysdeps/pthread
> -Isysdeps/pthread -Inptl/sysdeps/unix/sysv -Inptl/sysdeps/unix
> -Isysdeps/unix/sysv/linux/mips/mips32 -Isysdeps/unix/sysv/linux/mips
> -Isysdeps/unix/sysv/linux -Isysdeps/gnu -Isysdeps/unix/common
> -Isysdeps/unix/mman -Isysdeps/unix/inet -Isysdeps/unix/sysv
> -Isysdeps/unix/mips/mips32 -Isysdeps/unix/mips -Isysdeps/unix
> -Isysdeps/posix -Isysdeps/mips/mips32 -Isysdeps/mips
> -Isysdeps/ieee754/flt-32 -Isysdeps/ieee754/dbl-64
> -Isysdeps/wordsize-32 -Isysdeps/mips/fpu -Isysdeps/ieee754
> -Isysdeps/generic/elf -Isysdeps/generic -nostdinc -isystem
> /usr/lib/gcc/i386-redhat-linux/4.1.0/include -isystem
> /home/shahzad/install/mipsel/include -xc - -o
> /home/shahzad/build-glibc-headers/bits/stdio_lim.hT
> cc1: error: unrecognized command line option "-mabi=32"
> 
> 
> 
> I did some search on google,but on most of links "-mabi=32" option was
> being used with cross-compiler for mips.
> Would you please tell me what is causing the problem.
> 
> 
> 
> 
> On 6/17/06, James E Wilson <wilson@specifix.com> wrote:
> > On Fri, 2006-06-16 at 05:22, kernel coder wrote:
> > > /home/shahzad/install//mipsel/sys-include -DHAVE_CONFIG_H -I.
> > > -I../../../gcc-4.1.0/libssp -I. -Wall -O2 -g -O2 -MT ssp.lo -MD -MP
> > > -MF .deps/ssp.Tpo -c ../../../gcc-4.1.0/libssp/ssp.c -o ssp.o
> > > ../../../gcc-4.1.0/libssp/ssp.c:46:20: error: fcntl.h: No such file or directory
> >
> > You can't build target libraries like libssp in a --without-headers
> > build.  It was luck that this happened to work with earlier gcc
> > releases, because previously we didn't have C language target libraries
> > in gcc.  The solution is to do
> >   make all-gcc
> >   make install-gcc
> > instead of just
> >   make all
> >   make install
> >
> > Please see Dan Kegel's crosstools package, which already knows how to do
> > this.
> > --
> > Jim Wilson, GNU Tools Support, http://www.specifix.com
> >
> >
> 

  reply	other threads:[~2006-06-19  7:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 12:22 gcc-4.1.0 cross-compile for MIPS kernel coder
2006-06-16 12:38 ` Ralf Roesch
2006-06-16 14:22   ` kernel coder
2006-06-16 15:41 ` Jonathan Day
2006-06-16 22:33 ` James E Wilson
2006-06-19  6:40   ` kernel coder
2006-06-19  7:19     ` Matej Kupljen [this message]
2006-06-23 19:01     ` James E Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1150701553.7203.9.camel@localhost.localdomain \
    --to=matej.kupljen@ultra.si \
    --cc=lhrkernelcoder@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=wilson@specifix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox