Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 8 Mar 2023 13:09:25 +0000
From: "Max R. Dechantsreiter" <max@...formancejones.com>
To: musl@...ts.openwall.com
Subject: Re: unknown type name '__gnuc_va_list'

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

For what it's worth:

[/home/maxd] 56> cat /proc/version
Linux version 4.19.0 (mockbuild@...lder1.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

albeit after running for about the expected time.

Are there other environment variables I should be concerned about?


On Wed, Mar 08, 2023 at 12:47:26PM +0000, Max R. Dechantsreiter wrote:
> On Wed, Mar 08, 2023 at 12:43:23PM +0000, Ralo Kossovo wrote:
> > On 3/8/23, Max R. Dechantsreiter <max@...formancejones.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>
> 

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.