public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug build/14253] Glibc does not build with SELinux support
Date: Wed, 20 Jun 2012 06:49:00 -0000 [thread overview]
Message-ID: <bug-14253-131-cDS4S26iCf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14253-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14253
--- Comment #5 from Andreas Jaeger <aj at suse dot de> 2012-06-20 06:48:48 UTC ---
Ok, you're using a newer version of the libs than I do - and I don't see the
problem:
libselinux1-2.0.91-18.1.x86_64
libsepol1-2.0.41-14.36.x86_64
--
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:[~2012-06-20 6:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 10:52 [Bug build/14253] New: " lailavrazda1979 at gmail dot com
2012-06-19 3:57 ` [Bug build/14253] " carlos_odonell at mentor dot com
2012-06-19 19:39 ` aj at suse dot de
2012-06-20 6:22 ` lailavrazda1979 at gmail dot com
2012-06-20 6:23 ` lailavrazda1979 at gmail dot com
2012-06-20 6:49 ` aj at suse dot de [this message]
2012-06-20 7:05 ` lailavrazda1979 at gmail dot com
2012-06-20 7:26 ` aj at suse dot de
2012-06-20 7:39 ` lailavrazda1979 at gmail dot com
2012-06-20 7:48 ` aj at suse dot de
2012-06-20 7:55 ` lailavrazda1979 at gmail dot com
2012-06-20 8:47 ` lailavrazda1979 at gmail dot com
2012-07-23 16:28 ` vapier at gentoo dot org
2012-12-03 23:58 ` carlos at systemhalted dot org
2013-02-20 6:30 ` vapier at gentoo dot org
2013-02-20 22:04 ` lailavrazda1979 at gmail dot com
2014-06-19 6:25 ` 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-14253-131-cDS4S26iCf@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).