From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org
Subject: Re: cross compilation of xtables fails
Date: Fri, 03 Dec 2010 14:32:22 +0000 [thread overview]
Message-ID: <4CF8FF76.8040709@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1012031522040.22038@obet.zrqbmnf.qr>
> The compile stage is unfortunately not useful here. The configure line
> is required. (If it is not in your shell history, you can find it at the
> top of config.log.)
>
As I already pointed out - I can't get it at present as it is on a
different computer which I could only access later this evening (or
later this afternoon - if I am lucky!).
What is evident from what I posted, though, is that for these 3 group of
files the arch-specific options which make the cross compilation
possible (-m32 -mtune and -march) are completely ignored and the gcc
statement generated by the m4 macros are therefore tying the produced
objects to the build architecture, which is wrong. This is without me
providing you with any other logs.
next prev parent reply other threads:[~2010-12-03 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 13:54 cross compilation of xtables fails Mr Dash Four
2010-12-03 13:58 ` Jan Engelhardt
2010-12-03 14:03 ` Mr Dash Four
2010-12-03 14:23 ` Jan Engelhardt
2010-12-03 14:32 ` Mr Dash Four [this message]
2010-12-03 14:39 ` Jan Engelhardt
2010-12-03 19:31 ` Mr Dash Four
2010-12-03 19:45 ` Jan Engelhardt
2010-12-03 19:52 ` Mr Dash Four
2010-12-03 19:54 ` Jan Engelhardt
2010-12-03 20:04 ` Mr Dash Four
2010-12-03 20:30 ` Jan Engelhardt
2010-12-03 21:02 ` Mr Dash Four
2010-12-03 21:22 ` Jan Engelhardt
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=4CF8FF76.8040709@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=jengelh@medozas.de \
--cc=netfilter@vger.kernel.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.