public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@mellanox.com>
To: Joseph Myers <joseph@codesourcery.com>, <libc-alpha@sourceware.org>
Subject: Re: Library directories for tilegx
Date: Fri, 04 Nov 2016 01:01:00 -0000	[thread overview]
Message-ID: <1e1c3a65-b62f-7736-3fb8-741aa6afe09f@mellanox.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611040037410.20687@digraph.polyomino.org.uk>

On 11/3/2016 6:43 PM, Joseph Myers wrote:
> TileGX GCC believes that 64-bit libraries go in lib/ and 32-bit libraries
> and dynamic linker go in lib32/.  But the glibc port does not use
> LIBC_SLIBDIR_RTLDDIR in the 32-bit case, meaning that both get installed
> in lib/ and building a biarch GCC blows up (as found when making my
> build-many-glibcs.py script support building all GNU/Linux glibc ABIs).
> What is the correct set of directories to use?

Yes, we discovered much too late that multi-endian systems are basically required to use /lib64 and /lib.  Instead, we used /lib for 64-bit and /lib32 for 32-bit.

I will have to go look at exactly how we contrive the 32-bit installation in our commercial build; we do some nasty cross-bootstrapping from x86, which as I'm sure you recall was particularly unpleasant back in the glibc 2.12 days (our current "tip" release for tilegx is still CentOS 6.8).  And for my ongoing git testing, I always just test from the build tree, so I never noticed that 32-bit wanted to install natively in /lib.

Thanks for noticing!

-- 
Chris Metcalf, Mellanox Technologies
http://www.mellanox.com

  reply	other threads:[~2016-11-04  1:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04  0:44 Joseph Myers
2016-11-04  1:01 ` Chris Metcalf [this message]
2016-11-04  1:08   ` Joseph Myers
2016-11-04  1:50     ` Chris Metcalf
2016-11-04 13:33       ` Joseph Myers
2016-11-04 15:12         ` Chris Metcalf
2016-11-07 16:26       ` Joseph Myers
2016-11-07 21:48         ` Chris Metcalf
2016-11-09  0:35   ` Joseph Myers
2016-11-14 20:12     ` Chris Metcalf
2016-11-14 22:59       ` Joseph Myers
2016-11-14 23:25         ` Chris Metcalf

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=1e1c3a65-b62f-7736-3fb8-741aa6afe09f@mellanox.com \
    --to=cmetcalf@mellanox.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).