From: Sam Ravnborg <sam@ravnborg.org>
To: Oleg Verych <olecom@gmail.com>
Cc: "Sam Ravnborg (kbuild list)" <linux-kbuild@vger.kernel.org>
Subject: Re: gcc 3.4.6 fails to build 2.6.25 due to offsetof() not digestible by gas
Date: Fri, 2 May 2008 08:08:13 +0200 [thread overview]
Message-ID: <20080502060813.GB19090@uranus.ravnborg.org> (raw)
In-Reply-To: <8499950a0805011848h713606e3mda5dd2aed31dfa91@mail.gmail.com>
On Fri, May 02, 2008 at 02:48:58AM +0100, Oleg Verych wrote:
> Sam, please, tell to those guys, that shell must be `bash`, as Roman wanted.
No - we want to be portable across as many setups as possible.
So forcing us to use bash is in the long run not a good solutions.
We should go for the least common denominator - busy-box could be the one.
Sam
next prev parent reply other threads:[~2008-05-02 6:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 5:07 gcc 3.4.6 fails to build 2.6.25 due to offsetof() not digestible by gas sampo
2008-05-01 12:06 ` Adrian Bunk
2008-05-01 15:05 ` sampo
2008-05-01 16:34 ` Adrian Bunk
2008-05-01 16:38 ` sampo
2008-05-01 16:53 ` Adrian Bunk
2008-05-01 17:10 ` sampo
2008-05-01 18:53 ` `sed`ing asm-offsets (Re: gcc 3.4.6 fails to build 2.6.25 due to offsetof() not digestible by gas) Oleg Verych
2008-05-01 21:42 ` Sam Ravnborg
2008-05-01 21:52 ` Oleg Verych
2008-05-01 22:54 ` Oleg Verych
2008-05-01 19:17 ` gcc 3.4.6 fails to build 2.6.25 due to offsetof() not digestible by gas Adrian Bunk
2008-05-01 21:39 ` Sam Ravnborg
2008-05-01 22:07 ` Adrian Bunk
2008-05-02 0:53 ` sampo
2008-05-02 1:48 ` Oleg Verych
2008-05-02 6:08 ` Sam Ravnborg [this message]
2008-05-02 10:56 ` Oleg Verych
2008-05-02 10:42 ` Sam Ravnborg
2008-05-02 11:25 ` source processing-friendly scripting Oleg Verych
2008-05-02 6:06 ` gcc 3.4.6 fails to build 2.6.25 due to offsetof() not digestible by gas Sam Ravnborg
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=20080502060813.GB19090@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=olecom@gmail.com \
/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