public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "robxu9 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/11311] New: xtrace and memusage don't build Date: Mon, 22 Feb 2010 23:25:00 -0000 [thread overview] Message-ID: <20100222232542.11311.robxu9@gmail.com> (raw) Hi, I've been trying to rebuild a fedora 12 glibc 2.11.1 SRPM using mock for the x86_64 arch, but it always fails at: DEBUG: + for i in '$RPM_BUILD_ROOT/usr/bin/{xtrace,memusage}' DEBUG: + sed -e s~=/lib64/libpcprofile.so~=/usr/lib64/libpcprofile.so~ -e s~=/lib64/libmemusage.so~=/usr/lib64/libmemusage.so~ -e 's~='\''/\\\$LIB/libpcprofile.so~='\''/usr/\\$LIB/libpcprofile.so~' -e 's~='\''/\\\$LIB/libmemusage.so~='\''/usr/\\$LIB/libmemusage.so~' -i /builddir/build/BUILDROOT/glibc-2.11.1-3.fc12.x86_64/usr/bin/memusage DEBUG: sed: can't read /builddir/build/BUILDROOT/glibc-2.11.1- 3.fc12.x86_64/usr/bin/memusage: No such file or directory DEBUG: error: Bad exit status from /var/tmp/rpm-tmp.ygMzgm (%install) help? -- Summary: xtrace and memusage don't build Product: glibc Version: 2.11 Status: NEW Severity: normal Priority: P2 Component: nptl AssignedTo: drepper at redhat dot com ReportedBy: robxu9 at gmail dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=11311 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-02-22 23:25 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-22 23:25 robxu9 at gmail dot com [this message] 2010-02-22 23:39 ` [Bug nptl/11311] " 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=20100222232542.11311.robxu9@gmail.com \ --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: linkBe 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).