From: Joseph Myers <joseph@codesourcery.com>
To: Steve Ellcey <sellcey@cavium.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Obsolete matherr, _LIB_VERSION, libieee.a
Date: Thu, 24 Aug 2017 12:32:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1708241230090.1920@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1503519708.28672.77.camel@cavium.com>
On Wed, 23 Aug 2017, Steve Ellcey wrote:
> I actually have a similar problem with tst-mallocstate and the
> malloc_get_state symbol. Currently I just remove that test from the makefile
> in order to skip it and I guess I can do the same for this test but we
> will need a solution to this problem at some point and I was wondering
> if you had any ideas.
>
> Earlier discussion about tst-mallocstate:
> https://sourceware.org/ml/libc-alpha/2016-12/msg00527.html
I think Florian's suggestion from that discussion is a good idea: generate
a makefile equivalent of abi-versions.h, so that you can write
conditionals in makefiles that are equivalent to SHLIB_COMPAT conditions
in C code.
Obviously this is not specific to ILP32 so should be proposed for master
independent of ILP32 - it's just as useful for other new ports such as
RISC-V (kernel port hopefully ready for upstream in the not too distant
future) or ARC (kernel port already upstream).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-08-24 12:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 21:30 Joseph Myers
2017-08-21 20:16 ` Adhemerval Zanella
2017-08-21 21:45 ` Joseph Myers
2017-08-21 20:32 ` Gabriel F. T. Gomes
2017-08-21 21:17 ` Joseph Myers
2017-08-23 20:21 ` Steve Ellcey
2017-08-24 9:27 ` Szabolcs Nagy
2017-08-24 12:32 ` Joseph Myers [this message]
2017-08-24 17:20 ` Steve Ellcey
2017-08-24 17:25 ` Joseph Myers
2017-08-24 17:44 ` Steve Ellcey
2017-08-24 18:08 ` Joseph Myers
2017-08-24 18:55 ` Florian Weimer
2017-08-24 21:06 ` Steve Ellcey
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.1708241230090.1920@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=sellcey@cavium.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).