mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Max R. Dechantsreiter" <max@performancejones.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] unknown type name '__gnuc_va_list'
Date: Wed, 8 Mar 2023 13:27:37 +0000	[thread overview]
Message-ID: <ZAiNSUYt1gC4JWng@localhost.localdomain> (raw)
In-Reply-To: <20230308132442.GO4163@brightrain.aerifal.cx>

On Wed, Mar 08, 2023 at 08:24:42AM -0500, Rich Felker wrote:
> On Wed, Mar 08, 2023 at 01:09:25PM +0000, Max R. Dechantsreiter wrote:
> > ....I got the "validation test" working by setting C_INCLUDE_PATH:
> > 
> > cat > hello.c <<EOF
> > #include <stdio.h>
> > int main()
> > {
> >   printf("Hello, world!\n");
> >   return 0;
> > }
> > EOF
> > echo $CPATH
> > # /home/maxd/GNU/opt/gnu/gcc-12.1.0/include:/usr/include
> > export C_INCLUDE_PATH=$CPATH
> > $INSTALL/bin/musl-gcc hello.c
> > ../a.out
> > # Hello, world!
> 
> I suspect you already had C_INCLUDE_PATH in your environment and gcc

Actually not - it was unset.

> was finding /usr/include via that despite the musl-gcc wrapper
> suppressing the default. You should unset C_INCLUDE_PATH, or if you
> really need to set it, ensure that any non-musl include paths (e.g.
> /usr/include) do not appear in C_INCLUDE_PATH or any -I, etc.
> 
> It's not clear to me whether the musl-gcc wrapper should try to do
> anything to suppress C_INCLUDE_PATH, since you might want it for
> adding intended paths when invoking the wrapper. Maybe it could be
> enhanced to remove known-bad pathss but that seems fragile.
> 
> > For what it's worth:
> > 
> > [/home/maxd] 56> cat /proc/version
> > Linux version 4.19.0 (mockbuild@builder1.eng.sw.ru) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Thu Dec 15 20:31:06 MSK 2022
> > [/home/maxd] 57>
> > 
> > However, my application built with this musl-gcc still ends with
> > 
> > Killed
> 
> This is probably just a bug in the application. You could run it under
> gdb to see. Are you using static or dynamic linking? I thought you
> wanted static but I don't see -static in your command line above.

I will check that, thanks.

> 
> Rich

  reply	other threads:[~2023-03-08 13:27 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
2023-03-08 13:09           ` Max R. Dechantsreiter
2023-03-08 13:24             ` Rich Felker
2023-03-08 13:27               ` Max R. Dechantsreiter [this message]
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=ZAiNSUYt1gC4JWng@localhost.localdomain \
    --to=max@performancejones.com \
    --cc=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).