From: Tejun Heo <tj@kernel.org>
To: Namhyung Kim <namhyung@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Build failure on CONFIG_DEBUG_FORCE_WEAK_PER_CPU?
Date: Tue, 05 Oct 2010 18:13:39 +0200 [thread overview]
Message-ID: <4CAB4EB3.50001@kernel.org> (raw)
In-Reply-To: <1286277111.1663.14.camel@leonhard>
Hello,
On 10/05/2010 01:11 PM, Namhyung Kim wrote:
> I am using system default toolchain which is:
>
> $ gcc --version
> gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3
>
> $ ld -v
> GNU gold (GNU Binutils for Ubuntu 2.20.1-system.20100303) 1.9
Hmmm... mines are
$ gcc --version
gcc (SUSE Linux) 4.5.0 20100604 [gcc-4_5-branch revision 160292]
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ ld -v
GNU ld (GNU Binutils; openSUSE 11.3) 2.20.0.20100122-6
> A minimal .config can be made easily by doing make allnoconfig and
> selecting CONFIG_DEBUG_INFO and CONFIG_DEBUG_FORCE_WEAK_PER_CPU.
> Attached mine for your convenience. Thanks :-)
and the same config builds just fine. Can you please try newer
compiler / linker? The config option hasn't caused any trouble till
now and allyesconfig is something which get regularly tested so I'm
skeptical this is a wide spread problem.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-10-05 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 7:23 Build failure on CONFIG_DEBUG_FORCE_WEAK_PER_CPU? Namhyung Kim
2010-10-05 9:25 ` Tejun Heo
2010-10-05 11:11 ` Namhyung Kim
2010-10-05 16:13 ` Tejun Heo [this message]
2010-10-07 7:15 ` Namhyung Kim
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=4CAB4EB3.50001@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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