public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gschafer at zip dot com dot au" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nscd/798] nscd Makefile minor problem
Date: Sun, 17 Jul 2005 05:36:00 -0000	[thread overview]
Message-ID: <20050717053629.32472.qmail@sourceware.org> (raw)
In-Reply-To: <20050323054824.798.gschafer@zip.com.au>


------- Additional Comments From gschafer at zip dot com dot au  2005-07-17 05:36 -------
(In reply to comment #2)
> I've applied some patch although I have no sympathy for anybody using
> --with-headers.  That option is really only for the initial port.

Ulrich, thanks for fixing this. However, there is still a small problem. Those
lines need to be inside the

  ifeq (yes,$(have-selinux))

for the fix to be effective. It seems there is a mis-placed `endif'. I'll attach
a tiny patch to correct it.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |


http://sources.redhat.com/bugzilla/show_bug.cgi?id=798

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2005-07-17  5:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23  5:48 [Bug nscd/798] New: " gschafer at zip dot com dot au
2005-03-23  5:49 ` [Bug nscd/798] " gschafer at zip dot com dot au
2005-04-29  2:09 ` drepper at redhat dot com
2005-07-17  5:36 ` gschafer at zip dot com dot au [this message]
2005-07-17  5:38 ` gschafer at zip dot com dot au
2005-07-20 18:10 ` drepper 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=20050717053629.32472.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --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).