public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Mark Salter <msalter@redhat.com>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH] am33: bring port up to date with NPTL support
Date: Mon, 18 Jun 2012 15:41:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1206181535080.4626@digraph.polyomino.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1206181450580.4626@digraph.polyomino.org.uk>

Another point: you don't have a syscalls.list for am33, so as a 32-bit 
architecture that means you'll probably be missing prlimit64 and 
fanotify_mark (as generating ABI baselines, and comparing them with those 
for other architectures, might show).  So you should add one - and an 
appropriate Versions file to put those functions in the version actually 
adding them for am33.

Regarding versions - shlib-versions should ideally be set up to avoid 
symbols at versions that didn't exist in working form for am33.  See how 
Tile avoids versions before 2.12, and between 2.12 and 2.15.  If you 
haven't had any versions between 2.9 and 2.16 you could cause intermediate 
symbol versions not to exist for am33, for example (you might need to 
declare explicitly all past symbol versions that should exist for am33; 
I'm not sure).

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2012-06-18 15:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 14:47 Mark Salter
2012-06-18 15:23 ` Joseph S. Myers
2012-06-18 15:41   ` Joseph S. Myers [this message]
2012-06-18 17:00   ` Joseph S. Myers
2014-01-21 22:53 ` Joseph S. Myers
2014-01-21 23:40   ` Mark Salter
2014-01-22  0:02     ` Joseph S. Myers

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=Pine.LNX.4.64.1206181535080.4626@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=msalter@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).