From: Christoph Spielmann <spielc@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] ./configure --prefix /opt --host=armv5tel-softfloat-linux-gnueabi
Date: Mon, 15 Jun 2009 11:50:44 +0200 [thread overview]
Message-ID: <4A361974.8000800@gmail.com> (raw)
In-Reply-To: <4A3615F6.20104@toth.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2516 bytes --]
Hi Stephen!
I guess you installed a cross-compiler using crossdev (thus you should
be able to call your cross-compiler using
armv5tel-softfloat-linux-gnueabi-gcc).
Now if you install and setup crossdev-wrappers (emerge
crossdev-wrappers) and run emerge-wrapper --init, you'll get a directory
under /usr and a wrapper for emerge
(emerge-armv5tel-softfloat-linux-gnueabi) which you can use to
"cross-emerge" stuff.
On 15.06.2009 11:35, Stephen Feyrer wrote:
> Hi again
>
> Bah Hum-Bug! make failed. I guess some of those tests are important.
>
> I'm interested in crossdev wrappers but how can I make it apply to my
> current problem?
>
> --
> Boldly going forwards...
>
> Stephen.
>
> Stephen Feyrer wrote:
>
>> Hi Sven.
>>
>
>
>> I had get some other cached values:
>>
>> i_cv_epoll_works=no i_cv_inotify_works=no i_cv_posix_fallocate_works=no
>> i_cv_signed_size_t=no i_cv_gmtime_max_time_t=32 i_cv_signed_time_t=yes
>> i_cv_mmap_plays_with_write=yes i_cv_fd_passing=yes
>> i_cv_c99_vsnprintf=yes lib_cv_va_copy=yes lib_cv___va_copy=yes
>> lib_cv_va_val_copy=yes ./configure --prefix=/opt
>> --host=armv5tel-softfloat-linux-gnueabi
>>
>
>
>> :-) I'm now running make.
>>
>
>
>> Sven Rebhan wrote:
>>
>>> 2009/6/15 Stephen Feyrer<steve@toth.org.uk>:
>>>
>
>
>>> Hello Stephen,
>>>
>>>> checking whether we can use epoll... configure: error: in
>>>> `/root/dovecot/dovecot-1-2-6c0fb914e03e':
>>>> configure: error: cannot run test program while cross compiling
>>>> See `config.log' for more details.
>>>>
>
>
>>> I would strongly suggest to use crossdev-wrappers for this kind of
>>> jobs, as it automatically cares about this kind of problems.
>>>
>
>
>>> However, you might want to fix this problem yourself, so here we go. When
>>> cross-compiling, target programs can not be executed as they are
>>> probably compiled for an incompatible architecture (as the error
>>> states).
>>>
>
>
>>> Hence, you have to provide the result of the program run
>>> yourself using autoconf-cache values. Try to do the following:
>>>
>
>
>>> i_cv_epoll_works=yes ./configure --prefix=/opt
>>> --host=armv5tel-softfloat-linux-gnueabi
>>>
>
>
>>> Please check if epoll really works in your setup and change the value
>>> to "no" if it doesn't.
>>>
>
>
>>> Have fun!
>>>
>
>
>>> Sven
>>>
>
>
>> Thanks.
>>
>
>
>> --
>> Stephen
>>
>
>
>
[-- Attachment #2: Type: text/html, Size: 4505 bytes --]
next prev parent reply other threads:[~2009-06-15 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 22:39 [gentoo-embedded] ./configure --prefix /opt --host=armv5tel-softfloat-linux-gnueabi Stephen Feyrer
2009-06-15 7:08 ` Sven Rebhan
2009-06-15 8:56 ` Stephen Feyrer
2009-06-15 9:05 ` Sven Rebhan
2009-06-15 9:35 ` Stephen Feyrer
2009-06-15 9:50 ` Christoph Spielmann [this message]
2009-06-15 10:20 ` Stephen Feyrer
2009-06-15 11:14 ` Sven Rebhan
2009-06-15 11:58 ` Stephen Feyrer
2009-06-15 12:15 ` Stephen Feyrer
2009-06-15 12:36 ` Stephen Feyrer
2009-06-15 13:38 ` Ned Ludd
2009-07-20 23:00 ` Stephen Feyrer
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=4A361974.8000800@gmail.com \
--to=spielc@gmail.com \
--cc=gentoo-embedded@lists.gentoo.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