public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Steven Munroe <munroesj@us.ibm.com>
To: Roland McGrath <roland@redhat.com>,
	GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Broken build from libc cvs trunk
Date: Mon, 27 Feb 2006 20:52:00 -0000	[thread overview]
Message-ID: <440368AD.3010308@us.ibm.com> (raw)

Roland are you in the middle of rearranging the lowlevellocking support?

CVS trunk is broken with:

../nptl/lowlevellock.h:46: error: redefinition of ‘__generic_mutex_lock’
../nptl/lowlevellock.h:46: error: previous definition of
‘__generic_mutex_lock’ was here
../nptl/lowlevellock.h:76: error: redefinition of ‘__generic_mutex_unlock’
../nptl/lowlevellock.h:76: error: previous definition of
‘__generic_mutex_unlock’ was here

Is there something the platforms need to do? or should we just stay out
of your way ;-)

             reply	other threads:[~2006-02-27 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 20:52 Steven Munroe [this message]
2006-02-27 20:56 ` Roland McGrath
2006-02-27 21:06   ` Steve Munroe

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=440368AD.3010308@us.ibm.com \
    --to=munroesj@us.ibm.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@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).