public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Mike Frysinger <vapier@gentoo.org>, <libc-ports@sourceware.org>
Subject: Re: [PATCH] hppa: use hidden_def with internal pthread funcs
Date: Tue, 20 Nov 2012 23:42:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1211202339100.22161@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAE2sS1hH_vF1PbS29Oh_stg3_S0Wr3vfUS9DpVOX=G1jqgLUXQ@mail.gmail.com>

On Tue, 20 Nov 2012, Carlos O'Donell wrote:

> Thanks, that is correct and matches my list of remaining things that
> need fixing.

Add creating a sotruss-lib.c file as well.  (The lack of sotruss-lib.c 
support is an issue for powerpc, sh, s390 among libc targets - only the 
other libc targets have support directly in the elf/ file - as well as 
alpha am33 hppa ia64 m68k mips.  It came to my attention in my ongoing 
cleanup of compiler warnings from the MIPS build.  So if you clean up 
compiler warnings building for hppa - and I think that is something 
architecture maintainers ought to review for each release, as well as test 
results - then the lack of sotruss-lib.c support will show up for you as 
well.)

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2012-11-20 23:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18  9:04 Mike Frysinger
2012-11-19  5:46 ` Mike Frysinger
2012-11-19  5:48   ` Carlos O'Donell
2012-11-19  6:11     ` Mike Frysinger
2012-11-19  6:19       ` Carlos O'Donell
2012-11-19 14:33     ` Joseph S. Myers
2012-11-20 20:22       ` Carlos O'Donell
2012-11-20 23:42         ` Joseph S. Myers [this message]
2012-11-21  5:11           ` Carlos O'Donell
2012-11-19  5:46 ` Carlos O'Donell

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.1211202339100.22161@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=carlos@systemhalted.org \
    --cc=libc-ports@sourceware.org \
    --cc=vapier@gentoo.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).