From: "Max R. Dechantsreiter" <max@performancejones.com>
To: musl@lists.openwall.com
Subject: Re: [musl] unknown type name '__gnuc_va_list'
Date: Wed, 8 Mar 2023 12:47:26 +0000 [thread overview]
Message-ID: <ZAiD3tQkuBsbLPtK@localhost.localdomain> (raw)
In-Reply-To: <CAGg4HhQTaVCTcYBosdf7w5+CyEhW-PVt7Him=R--ZpZM9aYU7Q@mail.gmail.com>
On Wed, Mar 08, 2023 at 12:43:23PM +0000, Ralo Kossovo wrote:
> On 3/8/23, Max R. Dechantsreiter <max@performancejones.com> 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'?
[/home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/bin] 28> cat musl-gcc
#!/bin/sh
exec "${REALGCC:-gcc}" "$@" -specs "/home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/lib/musl-gcc.specs"
[/home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/bin] 29>
[/home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/lib] 31> cat musl-gcc.specs
%rename cpp_options old_cpp_options
*cpp_options:
-nostdinc -isystem /home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/include -isystem include%s %(old_cpp_options)
*cc1:
%(cc1_cpu) -nostdinc -isystem /home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/include -isystem include%s
*link_libgcc:
-L/home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/lib -L .%s
*libgcc:
libgcc.a%s %:if-exists(libgcc_eh.a%s)
*startfile:
%{!shared: /home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/lib/Scrt1.o} /home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/lib/crti.o crtbeginS.o%s
*endfile:
crtendS.o%s /home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/lib/crtn.o
*link:
-dynamic-linker /lib/ld-musl-x86_64.so.1 -nostdlib %{shared:-shared} %{static:-static} %{rdynamic:-export-dynamic}
*esp_link:
*esp_options:
*esp_cpp_options:
[/home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/lib] 32>
next prev parent reply other threads:[~2023-03-08 12:47 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
2023-03-08 12:47 ` Max R. Dechantsreiter [this message]
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:
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=ZAiD3tQkuBsbLPtK@localhost.localdomain \
--to=max@performancejones.com \
--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).