From: Richard Weinberger <richard@nod.at>
To: Florian Fainelli <florian@openwrt.org>
Cc: nico@openwrt.org, user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH 2/2] um: disable compile-time buffer checks
Date: Sun, 12 Jun 2011 13:56:14 +0200 [thread overview]
Message-ID: <201106121356.14546.richard@nod.at> (raw)
In-Reply-To: <201106121314.41348.florian@openwrt.org>
Am Sonntag 12 Juni 2011, 13:14:41 schrieb Florian Fainelli:
> From: Nicolas Thill <nico@openwrt.org>
>
> Ubuntu 8.10 and newer enable compile-time buffer checks by default,
> which can sometime cause build failures like this:
>
> LD vmlinux
> SYSMAP System.map
> SYSMAP .tmp_System.map
> LINK linux
> Building modules, stage 2.
> MODPOST 51 modules
> ERROR: "__sprintf_chk" [arch/um/drivers/harddog.ko] undefined!
Hmm, now I'm wondering why no other Ubuntu users have noticed this.
Are also current versions of Ubuntu affected?
Thanks,
//richard
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2011-06-12 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 11:14 [uml-devel] [PATCH 2/2] um: disable compile-time buffer checks Florian Fainelli
2011-06-12 11:56 ` Richard Weinberger [this message]
2011-06-12 21:52 ` Florian Fainelli
2011-06-12 22:56 ` Richard Weinberger
2011-06-13 12:39 ` Florian Fainelli
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=201106121356.14546.richard@nod.at \
--to=richard@nod.at \
--cc=florian@openwrt.org \
--cc=nico@openwrt.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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