public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "felix-glibc at fefe dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/10423] New: glibc does not build for ia64-linux
Date: Mon, 20 Jul 2009 23:49:00 -0000	[thread overview]
Message-ID: <20090720234852.10423.felix-glibc@fefe.de> (raw)

The first issue I'm running into is that bzero comes from sysdeps/ia64/bzero.S,
which declares bzero but not __bzero, which is referenced by a few RPC functions.
So in the end libc.so refuses to build with missing __bzero symbols.

After that there is another build failure, I'll paste the error message here:

/tmp/build/libc_pic.os: In function `faccessat':
(.text+0x130952): undefined reference to `fstatat64'
collect2: ld returned 1 exit status
make[1]: *** [/tmp/build/libc.so] Error 1

This should be self-explanatory.

-- 
           Summary: glibc does not build for ia64-linux
           Product: glibc
           Version: 2.11
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: felix-glibc at fefe dot de
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: x86_64-linux
  GCC host triplet: ia64-linux
GCC target triplet: ia64-linux


http://sourceware.org/bugzilla/show_bug.cgi?id=10423

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2009-07-20 23:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 23:49 felix-glibc at fefe dot de [this message]
2009-07-21  0:02 ` [Bug libc/10423] " felix-glibc at fefe dot de
2010-06-01  3:00 ` pasky at suse dot cz

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=20090720234852.10423.felix-glibc@fefe.de \
    --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).