linux-kernel - Re: [tip:x86/kbuild] x86: boot/compressed/vmlinux.lds.S: fix build of bzImage with 64 bit compiler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 30 Apr 2009 17:09:24 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	mingo@...hat.com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, tglx@...utronix.de, jdb@...x.dk,
	mingo@...e.hu, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/kbuild] x86: boot/compressed/vmlinux.lds.S: fix build of bzImage with 64 bit compiler

On Thu, Apr 30, 2009 at 07:52:55AM -0700, H. Peter Anvin wrote:
> tip-bot for Sam Ravnborg wrote:
> > Commit-ID:  83c4832683bc8ebcd1687b3c0bf3ba1ab253dd4f
> > Gitweb:     http://git.kernel.org/tip/83c4832683bc8ebcd1687b3c0bf3ba1ab253dd4f
> > Author:     Sam Ravnborg <sam@...nborg.org>
> > AuthorDate: Thu, 30 Apr 2009 12:03:16 +0200
> > Committer:  Ingo Molnar <mingo@...e.hu>
> > CommitDate: Thu, 30 Apr 2009 12:36:50 +0200
> > 
> > x86: boot/compressed/vmlinux.lds.S: fix build of bzImage with 64 bit compiler
> > 
> > Jesper reported that he saw following build issue:
> > 
> >  > ld:arch/x86/boot/compressed/vmlinux.lds:9: syntax error
> >  > make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 1
> >  > make[1]: *** [arch/x86/boot/compressed/vmlinux] Error 2
> >  > make: *** [bzImage] Error 2
> > 
> > CPP defines the symbol "i386" to "1".
> > Undefine this to fix it.
> > 
> 
> I'm wondering if we should build the *.lds.S with -ansi or some other
> gcc option which disables ALL non-underscore macros.

I did not know that -ansi had this effect.
We are only seldomly hitting this issue and I wonder
if it could break something in out included headers.
Most likely not.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/