Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jonathan Day <imipak@yahoo.com>
To: kernel coder <lhrkernelcoder@gmail.com>, linux-mips@linux-mips.org
Subject: Re: gcc-4.1.0 cross-compile for MIPS
Date: Fri, 16 Jun 2006 08:41:54 -0700 (PDT)	[thread overview]
Message-ID: <20060616154154.74837.qmail@web31513.mail.mud.yahoo.com> (raw)
In-Reply-To: <f69849430606160522i12050d00n9a4a39810f13b8a0@mail.gmail.com>

Hi,

Two quick questions in return! :) First, did you use
the patches on the Linux From Scratch website, which
fixes problems with GCC in a MIPS environment?
(Although not using the MIPSEL environment myself, I'm
on a big-endiam system, I learned very quickly that
those patches really are essential.)

The second question is why 4.1.0? 4.1.1 fixes some
nasties, from what I understand, making that the
better of the 4.1.x branch. On the flip-side, 4.0.3 is
the last-known version of GCC that will compile G95
correctly, strongly hinting at remaining issues in
4.1.x that have the potential for generating incorrect
code. (I've not been able to build 4.2.x from SVN for
a while, although it adds some features I would love
to use.)

Jonathan Day

--- kernel coder <lhrkernelcoder@gmail.com> wrote:

> hi,
>    I'm trying to cross compile gcc-4.1.0 for mipsel
> platform.Following
> is the sequence of commands which i'm using.My host
> system is i686.
> 
> ../gcc-4.1.0/configure --target=mipsel
> --without-headres
> --prefix=/home/shahzad/install/ --with-newlib
> --enable-languages=c
> 
> make
> 
> But following error is generated
> 
> /home/shahzad/mips_gcc/./gcc/xgcc
> -B/home/shahzad/mips_gcc/./gcc/
> -B/home/shahzad/install//mipsel/bin/
> -B/home/shahzad/install//mipsel/lib/ -isystem
> /home/shahzad/install//mipsel/include -isystem
> /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
> ../../../gcc-4.1.0/libssp/ssp.c: In function
> '__guard_setup':
> ../../../gcc-4.1.0/libssp/ssp.c:70: warning:
> implicit declaration of
> function 'open'
> ../../../gcc-4.1.0/libssp/ssp.c:70: error:
> 'O_RDONLY' undeclared
> (first use in this function)
> ../../../gcc-4.1.0/libssp/ssp.c:70: error: (Each
> undeclared identifier
> is reported only once
> ../../../gcc-4.1.0/libssp/ssp.c:70: error: for each
> function it appears in.)
> ../../../gcc-4.1.0/libssp/ssp.c:73: error: 'ssize_t'
> undeclared (first
> use in this function)
> ../../../gcc-4.1.0/libssp/ssp.c:73: error: expected
> ';' before 'size'
> .........................................
> ........................................
> 
> I'm using fedora 5 as development platform and
> version of gcc
> installed on system is 4.1.0
> 
> thanks,
> shahzad
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

  parent reply	other threads:[~2006-06-16 15:42 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 [this message]
2006-06-16 22:33 ` James E Wilson
2006-06-19  6:40   ` kernel coder
2006-06-19  7:19     ` Matej Kupljen
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=20060616154154.74837.qmail@web31513.mail.mud.yahoo.com \
    --to=imipak@yahoo.com \
    --cc=lhrkernelcoder@gmail.com \
    --cc=linux-mips@linux-mips.org \
    /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