mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Andrey Melnikov <temnota.am@gmail.com>
To: Rich Felker <dalias@aerifal.cx>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Re: move __BYTE_ORDER definition to alltypes.h
Date: Thu, 28 Jan 2021 15:45:08 +0300	[thread overview]
Message-ID: <CA+PODjrSGXXZTqSsZ2oVbZ5G=aYu6Bb_6OZEmiWuLn0H-5zvjQ@mail.gmail.com> (raw)
In-Reply-To: <20210127154506.GH23432@brightrain.aerifal.cx>

ср, 27 янв. 2021 г. в 18:45, Rich Felker <dalias@aerifal.cx>:
>
> On Wed, Jan 27, 2021 at 11:12:41AM +0300, Andrey Melnikov wrote:
> > ср, 27 янв. 2021 г. в 00:40, Rich Felker <dalias@aerifal.cx>:
> > >
> > > On Wed, Jan 27, 2021 at 12:29:05AM +0300, Andrey Melnikov wrote:
> > > > вт, 26 янв. 2021 г. в 20:23, Rich Felker <dalias@aerifal.cx>:
> > > > >
> > > > > On Tue, Jan 26, 2021 at 02:55:09PM +0300, Andrey Melnikov wrote:
> > > > > > Hi.

[...]

>
> Again, you cannot use libc headers for building the kernel or kernel
> modules. musl is not glibc. It uses a BSD-like include order and
> defines all of the headers itself rather than using a mix of gcc
> headers and libc-provided ones.
I'm already able to build kernel, modules and other stuff after
removing the installed by musl stdarg.h.

> Add -nostdinc and -I the gcc header path (like the kernel's own build system does) or you will hit obscure
> problems like this again even if changes are made to the endian macros that make your immediate problem go away.
stdarg.h is a compiler-specific thing, and -nostdinc disables that
patch too. Search, where located RIGHT stdarg.h - not trivial.

For me - patching ONE library with broken design is preferred, rather
than search in all other programs where authors define by itself
"reserved identifier for ANY USE" and patch it.
Thnx. But, if you think what linux kernel have broken design and
misuse defines  - you may tell kernel developers about that.

      reply	other threads:[~2021-01-28 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+PODjoUKSfu1Z+b2PukoVOKOCrfzhLAkDa2VOjvNQYnd9Hc1A@mail.gmail.com>
2021-01-26 17:23 ` Rich Felker
2021-01-26 21:29   ` Andrey Melnikov
2021-01-26 21:40     ` Rich Felker
2021-01-27  8:12       ` Andrey Melnikov
2021-01-27 15:45         ` Rich Felker
2021-01-28 12:45           ` Andrey Melnikov [this message]

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='CA+PODjrSGXXZTqSsZ2oVbZ5G=aYu6Bb_6OZEmiWuLn0H-5zvjQ@mail.gmail.com' \
    --to=temnota.am@gmail.com \
    --cc=dalias@aerifal.cx \
    --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).