mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Ralo Kossovo <>
Subject: Re: [musl] unknown type name '__gnuc_va_list'
Date: Wed, 8 Mar 2023 12:43:23 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <ZAhxEMpQkiyZ/Udu@localhost.localdomain>

On 3/8/23, Max R. Dechantsreiter <> wrote:

> so how is it that prefix=/usr/local/musl?
> Likewise exec_prefix should not be in system space.

To my knowledge, these defaults get overwritten by 'config.mak' when
it gets included on 'Makefile:78'. That is so that the 'Makefile'
routines get preserved across iterations and work only with changing
variable values, I believe. Essentially, it makes everything more
straight-forward and deterministic - a reason why I was able to refer
you to a specific line of the Makefile.
Feel free to correct me on this if I'm wrong.

Could you, please, share with us the contents of
'$(prefix)/bin/musl-gcc' and '$(prefix)/lib/musl-gcc.specs'?

  reply	other threads:[~2023-03-08 12:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 13:48 Max R. Dechantsreiter
2023-03-07 19:37 ` Szabolcs Nagy
2023-03-07 20:28 ` Ralo Kossovo
2023-03-08 11:21   ` Max R. Dechantsreiter
2023-03-08 11:27     ` Max R. Dechantsreiter
2023-03-08 12:43       ` Ralo Kossovo [this message]
2023-03-08 12:47         ` Max R. Dechantsreiter
2023-03-08 13:09           ` Max R. Dechantsreiter
2023-03-08 13:24             ` Rich Felker
2023-03-08 13:27               ` Max R. Dechantsreiter
2023-03-08 13:51             ` Ralo Kossovo
2023-03-08 14:10               ` Max R. Dechantsreiter
2023-03-08 14:52                 ` Ralo Kossovo
2023-03-08 15:36                   ` Max R. Dechantsreiter
2023-03-09  6:48                     ` Ralo Kossovo

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* 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

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).