From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: New gcc wrapper to try
Date: Sun, 22 Apr 2012 22:57:04 -0700 [thread overview]
Message-ID: <20120422225704.75a67b0b@newbook> (raw)
In-Reply-To: <20120421203751.GG14673@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
On Sat, 21 Apr 2012 16:37:51 -0400
Rich Felker <dalias@aerifal.cx> wrote:
> Here's an updated version which fixes some issues with the previous
> (wrong crtbegin/end files when -shared is used, etc.)
>
Doesn't fix building wireless-tools (I've changed the target directory
to fit my install; no other changes)
In fact, where the old musl-gcc can link the object-file statically,
this one cannot link it at all, under any circumstances.
(This version is saved as muslcc, if you want to examine the logs...)
Using make iwmulticall
Isaac Dunham
[-- Attachment #2: make.muslcc --]
[-- Type: application/octet-stream, Size: 2529 bytes --]
muslcc -Os -W -Wall -Wstrict-prototypes -I. -DIW_USES_ITS_OWN_DOGFOOD -I/opt/musl/linux-headers/include -D_GNU_SOURCE -MMD -c iwmulticall.c
In file included from iwmulticall.c:96:
iwgetid.c: In function ‘print_one_device’:
iwlib.c:2161: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib.c:2161: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib.c:2162: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib.c:2162: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib.c:2163: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib.c:2163: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwgetid.c:178: note: initialized from here
In file included from iwmulticall.c:74:
iwlist.c: In function ‘print_scanning_info’:
iwlib.c:2163: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib.c:2163: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib.c:2162: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib.c:2162: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib.c:2161: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib.c:2161: warning: dereferencing pointer ‘({anonymous})’ does break strict-aliasing rules
iwlib-private.h:121: note: initialized from here
muslcc -Wl,-s -Os -W -Wall -Wstrict-prototypes -I. -DIW_USES_ITS_OWN_DOGFOOD -I/opt/musl/linux-headers/include -D_GNU_SOURCE -MMD -o iwmulticall iwmulticall.o -lm
iwmulticall.o: In function `set_commit_info':
iwmulticall.c:(.text+0x11d): undefined reference to `__stack_chk_fail'
iwmulticall.o: In function `iw_check_if_addr_type':
iwmulticall.c:(.text+0x21a): undefined reference to `__stack_chk_fail'
iwmulticall.o: In function `iw_check_mac_addr_type':
iwmulticall.c:(.text+0x295): undefined reference to `__stack_chk_fail'
iwmulticall.o: In function `print_iface_version_info':
iwmulticall.c:(.text+0x3a0): undefined reference to `__stack_chk_fail'
iwmulticall.o: In function `set_sens_info':
iwmulticall.c:(.text+0x426): undefined reference to `__stack_chk_fail'
iwmulticall.o:iwmulticall.c:(.text+0xcff): more undefined references to `__stack_chk_fail' follow
collect2: ld returned 1 exit status
make: *** [iwmulticall] Error 1
next prev parent reply other threads:[~2012-04-23 5:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 6:49 Rich Felker
2012-04-21 20:37 ` Rich Felker
2012-04-23 5:57 ` Isaac Dunham [this message]
2012-04-23 9:19 ` Rich Felker
2012-04-24 19:28 ` Isaac Dunham
2012-04-24 19:45 ` Isaac Dunham
2012-04-24 21:28 ` Solar Designer
2012-04-24 21:41 ` Rich Felker
2012-04-24 22:10 ` Rich Felker
2012-04-24 22:14 ` Solar Designer
2012-04-24 23:53 ` Szabolcs Nagy
2012-04-25 1:21 ` Solar Designer
2012-04-21 22:45 ` Isaac Dunham
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=20120422225704.75a67b0b@newbook \
--to=idunham@lavabit.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).