[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170126145352.GF1533@brightrain.aerifal.cx>
Date: Thu, 26 Jan 2017 09:53:52 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Providing <sgidefs.h> for MIPS?
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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
