From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 11845 invoked from network); 8 Mar 2023 13:24:59 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 8 Mar 2023 13:24:59 -0000 Received: (qmail 1513 invoked by uid 550); 8 Mar 2023 13:24:55 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 1478 invoked from network); 8 Mar 2023 13:24:55 -0000 Date: Wed, 8 Mar 2023 08:24:42 -0500 From: Rich Felker To: "Max R. Dechantsreiter" Cc: musl@lists.openwall.com Message-ID: <20230308132442.GO4163@brightrain.aerifal.cx> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] unknown type name '__gnuc_va_list' 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 < #include > 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 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. Rich