From: Kukjin Kim <kgene.kim@samsung.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
linux-kernel@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
viro@zeniv.linux.org.uk
Subject: Re: error: 'SEGMENT_SIZE' undeclared with arm-eabi-gcc toolchain
Date: Mon, 02 Apr 2012 12:14:46 -0700 [thread overview]
Message-ID: <4F79FAA6.8060900@samsung.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1203310017440.24151@xanadu.home>
Nicolas Pitre wrote:
> On Fri, 30 Mar 2012, Kukjin Kim wrote:
>
[...]
Hi Nicolas,
> So the clue you're looking for is probably on the 18th line above.
>
Ah Yep, I see.
> BTW, no one is using a.out on ARM anymore. You should really consider
> removing CONFIG_BINFMT_AOUT from your config.
>
Oh, now s3c2410_defconfig has it. OK, let me fix it.
Thank you for your time and kindly explanation.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2012-04-02 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 22:50 error: 'SEGMENT_SIZE' undeclared with arm-eabi-gcc toolchain Kukjin Kim
2012-03-31 4:58 ` Nicolas Pitre
2012-04-02 19:14 ` Kukjin Kim [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=4F79FAA6.8060900@samsung.com \
--to=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=viro@zeniv.linux.org.uk \
/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