public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bgs.jr at comcast dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14542] New: HFS+ Filesystem Incompatibility
Date: Mon, 03 Sep 2012 18:04:00 -0000 [thread overview]
Message-ID: <bug-14542-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14542
Bug #: 14542
Summary: HFS+ Filesystem Incompatibility
Product: glibc
Version: 2.16
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: unassigned@sourceware.org
ReportedBy: bgs.jr@comcast.net
CC: drepper.fsp@gmail.com
Classification: Unclassified
libc_pic.so have invalid symbols, as well as, librtld when compiling on hfsplus
filesystems, on both x86_64 and i686. I am using amd64. Linux from scratch
versions, 7.0, 7.1, 7.2. GCC 4.6.1, 4.6.2, 4.7.1. Glibc 2.14.1, and 2.16.0 and
binutils 2.22, kernel 3.2.6 and 3.5.2. On X86_64 I get an error stating librtld
needed to be recompiled with -fPIC then compiling again, I get a very similar
error without a direction to compile with -fPIC. So I tried other versions of
glibc and got the same result. Then tried other versions of gcc and binutils
and got the same result. So I then tried all of the steps on i686 and got an
error in the same context, i686_GOT_OFF relocation error. Then I tried to
install glibc again on ext4 filesystem, and compiled cleanly the first time.
--
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 reply other threads:[~2012-09-03 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 18:04 bgs.jr at comcast dot net [this message]
2012-09-03 20:06 ` [Bug libc/14542] " aj at suse dot de
2014-06-17 4:47 ` 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-14542-131@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).