mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Providing <sgidefs.h> for MIPS?
Date: Thu, 26 Jan 2017 09:53:52 -0500	[thread overview]
Message-ID: <20170126145352.GF1533@brightrain.aerifal.cx> (raw)
In-Reply-To: <52a24746-2e25-9e4d-0b52-9ba026417ef4@att.net>

On Wed, Jan 25, 2017 at 11:31:27PM -0800, Alexey Neyman wrote:
> Hi,
> 
> In crosstool-ng, a failure to build native GDB for mips-*-mips has
> been reported: https://github.com/crosstool-ng/crosstool-ng/pull/517
> 
> The reason is a missing <sgidefs.h> header (which is provided by
> glibc/uClibc, but not by musl). The reporter suggested to use
> <asm/sgidefs.h> from the Linux kernel instead. However, GDB
> developers seem to disagree:
> https://sourceware.org/ml/gdb-patches/2017-01/msg00446.html; their
> view is that the <sgidefs.h> header is to be provided as a part of
> the user-space headers.
> 
> Should musl provide one?

I don't think so. This is a legacy OS-vendor-specific header that
should not be provided or used at all, much less in musl. An easy way
for distros to make gdb happy would be just to ship an sgidefs.h, but
really gdb should be using the compiler-predefined macros (e.g.
_MIPS_SIM, _ABI64, etc. like musl's configure script does) rather than
a silly SGI header that just provides the same things by different
names, unless the OS part of the tuple is irix.

Rich


  reply	other threads:[~2017-01-26 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26  7:31 Alexey Neyman
2017-01-26 14:53 ` Rich Felker [this message]
2017-02-04 20:49 ` Alexey Neyman

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=20170126145352.GF1533@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).