public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12858] cannot build
Date: Thu, 09 Jun 2011 17:01:00 -0000 [thread overview]
Message-ID: <bug-12858-131-0mEHkqijIX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12858-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12858
Paul Pluzhnikov <ppluzhnikov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppluzhnikov at google dot
| |com
--- Comment #2 from Paul Pluzhnikov <ppluzhnikov at google dot com> 2011-06-09 17:01:02 UTC ---
(In reply to comment #0)
> After a succesful configure, make generates the following errors:
>
> In file included from ../sysdeps/unix/sysv/linux/syslog.c:10:
> ../misc/syslog.c: In function ‘__vsyslog_chk’:
> ../misc/syslog.c:123: sorry, unimplemented: inlining failed in call to
> ‘syslog’: function body not available
I've seen this failure when trying to build glibc with gcc that automatically
defines _FORTIFY_SOURCE (which, I believe, some Ubuntu-distributed gcc's do).
Adding -U_FORTIFY_SOURCE to CFLAGS may help.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-06-09 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 22:55 [Bug libc/12858] New: " matteosistisette at gmail dot com
2011-06-08 23:32 ` [Bug libc/12858] " drepper.fsp at gmail dot com
2011-06-09 17:01 ` ppluzhnikov at google dot com [this message]
2014-06-13 14:38 ` fweimer at redhat dot com
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=bug-12858-131-0mEHkqijIX@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).