From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Malek <souf_oued@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] cross-compiling
Date: Thu, 02 Oct 2008 17:11:22 +0200 [thread overview]
Message-ID: <48E4E49A.3050206@domain.hid> (raw)
In-Reply-To: <48E4E3E9.3020907@domain.hid>
Malek wrote:
> Gilles Chanteperdrix a écrit :
>> Malek wrote:
>>> $ ./configure --target=i686-linux --host=i686-linux --build=i386-pc-linux-gnu
>>> --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc --prefix=/usr/xenomai
>>> --disable-smp --disable-x86-sep --enable-x86-tsc
>>> ====================================================================
>>> (...)
>>> The architecture of the host is x86 under (cross)uClibc (0.9.29), (cross)GCC: 4.2.4,
>>> (cross)binutils 2.18.50.0.1, Xenomai 2.4.5.
>> So, you are compiling on x86 for x86 ? You are not cross-compiling then.
> Possible !!!
>> If your host is x86_64 and you are compiling for x86_32, you should pass
>> the -m32 option to gcc.
>>
> My host is x86_32 (Fedora 9) also but I do not use gcc that comes with Fedora,
> I used Buildroot(http://buildroot.uclibc.org) to produce an isolated compilation
> environment for another x86_32, it looks like LFS (Linux From Scratch).
LFS meant LARGEFILE_SOURCE or Large File Support, or something like that.
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
That is the problem I suspected. Will fix, thanks for reporting.
--
Gilles.
prev parent reply other threads:[~2008-10-02 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 10:47 [Xenomai-help] cross-compiling Malek
2008-10-02 12:05 ` Gilles Chanteperdrix
[not found] ` <48E4D3A6.5010401@domain.hid>
2008-10-02 14:30 ` Gilles Chanteperdrix
[not found] ` <48E4D6E2.1030309@domain.hid>
2008-10-02 15:08 ` Malek
2008-10-02 15:11 ` Gilles Chanteperdrix [this message]
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=48E4E49A.3050206@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=souf_oued@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.