From: Dan Kegel <dank@kegel.com>
To: CLEBER Vinicius Ribeiro de Almeida <cleber.vinicius@cimatec.fieb.org.br>
Cc: RAFAEL de Brito Tavares Lima <RAFAELd@cimatec.fieb.org.br>,
crossgcc <crossgcc@sourceware.org>
Subject: Re: Problems about CROSSTOOL for ARM architecture on Linux Ubuntu
Date: Sat, 30 May 2009 12:07:00 -0000 [thread overview]
Message-ID: <a71bd89a0905291339v6a10648dm339729443cd343bb@mail.gmail.com> (raw)
In-Reply-To: <5B0E5196613D1341A952944FDCCC4EB601D83FCB@cimatec-mail.fieb.org.br>
[+crossgcc]
<cleber.vinicius@cimatec.fieb.org.br> wrote:
> ... working on a workstation that runs an Ubuntu 8.10. I
> was trying to use your crosstool for ARM architecture (ARM9), but it’s
> presenting some problems in the compilation process.
>
> $ sh demo-arm.sh
> ...
> ... /opt/crosstool/build/arm-linux/gcc-3.4.5-glibc-2.3.6/gcc-3.4.5/gcc/collect2.c
> -o collect2.o
>
> In function open:
>
> inlined from collect_execute at
> /opt/crosstool/build/arm-linux/gcc-3.4.5-glibc-2.3.6/gcc-3.4.5/gcc/collect2.c:1537:
>
> /usr/include/bits/fcntl2.h:51: error: call to __open_missing_mode
> declared with attribute error: open with O_CREAT in second argument needs 3
> arguments
I guess you'd need to drop a patch into patches/gcc-3.4.5 containing
something like the patch in
http://www.freelists.org/post/haiku-development/buildtools-building-on-ubuntu-810
> I clean the line 1537 but the file returns without modifications!
That's because when you rerun demo.sh, it unpacks the source
and applies all patches again, overwriting any changes you made.
That's why you have to put a patch into the patches/gcc-3.4.5 directory
where it can be picked up by the script.
- Dan
--
For unsubscribe information see http://sourceware.org/lists.html#faq
parent reply other threads:[~2009-05-29 20:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5B0E5196613D1341A952944FDCCC4EB601D83FCB@cimatec-mail.fieb.org.br>]
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=a71bd89a0905291339v6a10648dm339729443cd343bb@mail.gmail.com \
--to=dank@kegel.com \
--cc=RAFAELd@cimatec.fieb.org.br \
--cc=cleber.vinicius@cimatec.fieb.org.br \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).