From: Gary Hughes-Fenchel <ghughesf@tibco.com>
To: linux-c-programming@vger.kernel.org
Subject: Problem linking with -D_FILE_OFFSET_BITS=64
Date: Thu, 02 Aug 2007 11:05:40 -0500 [thread overview]
Message-ID: <f8svck$g5d$1@sea.gmane.org> (raw)
I see this same problem on a 32 and 64 bit machine. When I build a
dynamic library I see the following error message ("reallysmall" is the
name of the executable my test program is attempting to build):
/usr/bin/ld: reallysmall: hidden symbol `stat64' in
/usr/lib64/libc_nonshared.a(stat64.oS) is referenced by DSO
collect2: ld returned 1 exit status
When I build a static lib (using ar rv) I see no such problem. If I
remove the -D_FILE_OFFSET_BITS=64 from the compilation the problem goes
away. Does anyone know what is happening? I have a small test program I
could send along if it would help.
(I apologize in advance if this is the wrong group to be sending this
question to. There does not seem to be an active libc group around.)
Gary Hughes-Fenchel
reply other threads:[~2007-08-02 16:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='f8svck$g5d$1@sea.gmane.org' \
--to=ghughesf@tibco.com \
--cc=linux-c-programming@vger.kernel.org \
/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 NNTP newsgroup(s).