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 14:10:31 +0000 [thread overview]
Message-ID: <ZAiXV8wmZ713RbkB@localhost.localdomain> (raw)
In-Reply-To: <CAGg4HhRkn0YTtpnO0RayNq0zBd9Q1nqgDqXD4_LktJH2pOFBxA@mail.gmail.com>
On Wed, Mar 08, 2023 at 01:51:35PM +0000, Ralo Kossovo wrote:
> On 3/8/23, Max R. Dechantsreiter <max@performancejones.com> wrote:
> > ...I got the "validation test" working by setting C_INCLUDE_PATH:
>
> There's got to be a cleaner way to fix this.
> What output does '$ echo | $(prefix)/bin/musl-gcc -E -Wp,-v -'
> generate? Does '$(prefix)/include' contain any files, in the first
> place?
[/home/maxd/GNU/Build/musl-1.2.3_gcc-12.1.0] 28> echo | $INSTALL/bin/musl-gcc -E -Wp,-v -
ignoring duplicate directory "/home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/include"
ignoring duplicate directory "/home/maxd/GNU/opt/gnu/gcc-12.1.0/lib/gcc/x86_64-linux-gnu/12.1.0/include"
ignoring duplicate directory "/home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/include"
as it is a non-system directory that duplicates a system directory
ignoring duplicate directory "/home/maxd/GNU/opt/gnu/gcc-12.1.0/include"
as it is a non-system directory that duplicates a system directory
ignoring duplicate directory "/usr/include"
as it is a non-system directory that duplicates a system directory
#include "..." search starts here:
#include <...> search starts here:
/home/maxd/GNU/lib/musl-1.2.3_gcc-12.1.0/include
/home/maxd/GNU/opt/gnu/gcc-12.1.0/lib/gcc/x86_64-linux-gnu/12.1.0/include
/home/maxd/GNU/opt/gnu/gcc-12.1.0/include
/usr/include
End of search list.
# 0 "<stdin>"
# 0 "<built-in>"
# 0 "<command-line>"
# 1 "<stdin>"
[/home/maxd/GNU/Build/musl-1.2.3_gcc-12.1.0] 29>
[/home/maxd/GNU/Build/musl-1.2.3_gcc-12.1.0] 29> ls $INSTALL/include
aio.h fcntl.h libintl.h pthread.h stddef.h time.h
alloca.h features.h limits.h pty.h stdint.h uchar.h
ar.h fenv.h link.h pwd.h stdio_ext.h ucontext.h
arpa float.h locale.h regex.h stdio.h ulimit.h
assert.h fmtmsg.h malloc.h resolv.h stdlib.h unistd.h
bits fnmatch.h math.h sched.h stdnoreturn.h utime.h
byteswap.h ftw.h memory.h scsi string.h utmp.h
complex.h getopt.h mntent.h search.h strings.h utmpx.h
cpio.h glob.h monetary.h semaphore.h stropts.h values.h
crypt.h grp.h mqueue.h setjmp.h sys wait.h
ctype.h iconv.h net shadow.h syscall.h wchar.h
dirent.h ifaddrs.h netdb.h signal.h sysexits.h wctype.h
dlfcn.h inttypes.h netinet spawn.h syslog.h wordexp.h
elf.h iso646.h netpacket stdalign.h tar.h
endian.h langinfo.h nl_types.h stdarg.h termios.h
err.h lastlog.h paths.h stdbool.h tgmath.h
errno.h libgen.h poll.h stdc-predef.h threads.h
[/home/maxd/GNU/Build/musl-1.2.3_gcc-12.1.0] 30>
next prev parent reply other threads:[~2023-03-08 14:10 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
2023-03-08 13:51 ` Ralo Kossovo
2023-03-08 14:10 ` Max R. Dechantsreiter [this message]
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=ZAiXV8wmZ713RbkB@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).