From: Sam Ravnborg <sam@ravnborg.org>
To: sampo@symlabs.com
Cc: Adrian Bunk <bunk@kernel.org>, 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:06:45 +0200 [thread overview]
Message-ID: <20080502060645.GA19090@uranus.ravnborg.org> (raw)
In-Reply-To: <52649.81.193.128.196.1209689622.squirrel@galactus.symlabs.net>
On Fri, May 02, 2008 at 02:53:42AM +0200, sampo@symlabs.com wrote:
> Adrian Bunk wrote:
> > On Thu, May 01, 2008 at 11:39:52PM +0200, Sam Ravnborg wrote:
> >>
> >> Do we know why it picked up the busy box version?
>
> I think it has to do with my /bin/sh being the busybox ash. It seems
> the ash prefers its built-in version over the one in path. This is
> probably due to me having compiled busybox with some option. Sorry
> for the confusion.
This makes sense - thanks for the explanation!
> If I edit linux/Kbuild to reference explicitly /usr/bin/sed (which
> is the gnu sed), the compile proceeds ok up to a point where
> following happens
>
> (snip)
> make -f scripts/Makefile.build obj=arch/x86/vdso
> gcc -Wp,-MD,arch/x86/vdso/vdso32/.int80.o.d -nostdinc -isystem
> /apps/gcc/3.4.6/lib/gcc/i686-pc-linux-gnu/3.4.6/include -D__KERNEL__
> -Iinclude -include include/linux/autoconf.h -D__ASSEMBLY__ -m32
> -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1
> -Iinclude/asm-x86/mach-default -c -o arch/x86/vdso/vdso32/int80.o
> arch/x86/vdso/vdso32/int80.S
> arch/x86/vdso/vdso32/int80.S: Assembler messages:
> arch/x86/vdso/vdso32/int80.S:68: Fatal error: cannot write to output file
> make[1]: *** [arch/x86/vdso/vdso32/int80.o] Error 1
> make: *** [arch/x86/vdso] Error 2
I will assume this is sed that is playing tricks with us again.
If you replace sed with /usr/bin/sed in the arch/x86/vdso/Makefile
does the build then proceed?
If this does not fix it then try to post what happens a few lines
before the gcc invocation - this is likely where we start to see
the problem.
> I would wish at least busybox sed be accommodated. Looking at the
> sed expression, it seems unnecessarily complicated. I'll try to formulate
> a simpler expression that accomplishes the same net result, namely
> transforming
>
> ->IA32_SIGCONTEXT_ax $44 offsetof(struct sigcontext, ax)
>
> to
>
> #define IA32_SIGCONTEXT_ax 44 /* offsetof(struct sigcontext, ax) # */
>
> It can't be as difficult as
>
> "/^->/{s:^->\([^ ]*\) [\$$#]*\([^ ]*\) \(.*\):#define \1 \2 /* \3 */:;
> s:->::; p;}"
There a special mips case to consider too.
A patch is appreciated!
Sam
prev parent reply other threads:[~2008-05-02 6:06 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
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 ` Sam Ravnborg [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=20080502060645.GA19090@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=sampo@symlabs.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