unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Burton Samograd <burton.samograd@gmail.com>
To: emacs-devel@gnu.org
Subject: Build problem: Error: symbol `pread64' is already defined
Date: Sun, 04 Nov 2012 10:44:35 -0700	[thread overview]
Message-ID: <5096A983.5080807@gmail.com> (raw)

Hello,

I'm trying to build the current emacs git HEAD on one of my machines (Centos 5.8 on a VM host so I can't update it to a newer version) and I keep getting the following error:

gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I/root/src/emacs-git/lib -I../src -I/root/src/emacs-git/src      -g3 -O2 -MT careadlinkat.o -MD -MP -MF .deps/careadlinkat.Tpo -c -o careadlinkat.o careadlinkat.c
/tmp/cc2jQqUg.s: Assembler messages:
/tmp/cc2jQqUg.s:122: Error: symbol `pread64' is already defined

From what I can see this looks to be an issue with my libc headers (unistd.h most directly I think) .  The glibc on this  system is 2.5.81.el5_8.7 and I've recently done a 'yum update' to the current release for this Centos version.

I've done a side by side comparison of the section of unistd.h on two machines, one a current Ubuntu and the Centos one that is having problems; they are almost close to identical with only a 'if defined' guard that should have nothing to do with with the systems I am running on (I hope).

I've also updated my gcc to 4.7.2, the current release.

Any ideas on what might be causing this build problem on this specific machine and not others?  This isn't just with the current HEAD, but it's been going on for a few weeks now; I'm just finally getting around to reporting it.

--
Burton Samograd



             reply	other threads:[~2012-11-04 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-04 17:44 Burton Samograd [this message]
2012-11-04 17:47 ` Build problem: Error: symbol `pread64' is already defined Burton Samograd
2012-11-10 20:17   ` Burton Samograd

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5096A983.5080807@gmail.com \
    --to=burton.samograd@gmail.com \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).