From: Joseph Myers <joseph@codesourcery.com>
To: <libc-alpha@sourceware.org>, <cmetcalf@mellanox.com>
Subject: Library directories for tilegx
Date: Fri, 04 Nov 2016 00:44:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611040037410.20687@digraph.polyomino.org.uk> (raw)
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?
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2016-11-04 0:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 0:44 Joseph Myers [this message]
2016-11-04 1:01 ` Chris Metcalf
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=alpine.DEB.2.20.1611040037410.20687@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=cmetcalf@mellanox.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).