mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Rich Felker <dalias@libc.org>, musl@lists.openwall.com
Subject: Re: __write alias missing on arm platforms
Date: Thu, 22 Oct 2015 23:18:54 +0200	[thread overview]
Message-ID: <562952BE.7030501@dd-wrt.com> (raw)
In-Reply-To: <20151022205525.GZ8645@brightrain.aerifal.cx>

Am 22.10.2015 um 22:55 schrieb Rich Felker:
> On Thu, Oct 22, 2015 at 10:21:54PM +0200, Sebastian Gottschall wrote:
>> musl is missing the __write function which seem to be a alias to "write".
>> this is required by libgcc on arm platforms. under some conditions
>> the compiler will generate code which does reference
>> this function then which leads to unresolved symbols
>> (seen on squid 4.0.1 on xscale)
>>
>> /home/xfs/toolchains/toolchain-armeb_xscale_gcc-5.2.0_musl-1.1.11/bin/../lib64/gcc/armeb-openwrt-linux-muslgnueabi/5.2.0/libgcc.a(linux-atomic-64bit.o):
>> In function `__check_for_sync8_kernelhelper':
>> /home/xfs/openwrt/trunk2/trunk/build_dir/toolchain-armeb_xscale_gcc-5.2.0_musl-1.1.11/gcc-5.2.0/libgcc/config/arm/linux-atomic-64bit.c:59:
>> undefined reference to `__write'
>> collect2: error: ld returned 1 exit status
>> l
> __write is not a public API even in glibc as far as I can tell. This
> looks like an abuse of an accidentally-public symbol by libgcc. For
> musl target anyway it should just be patched out of libgcc, e.g. with
> #ifdef.
you mean i have to send a bug report to GCC maintainers? i its part if 
the libgcc sourcecode and is not provided by libgcc, but just referenced
i checked uclibc and glibc. both define __write as alias for write just 
because of libgcc

so lets declare musl as broken on arm if gcc is used, if this is a 
solution for you :-)

>
> Rich
>



  reply	other threads:[~2015-10-22 21:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  3:13 musl 1.1.12 released Rich Felker
2015-10-22 20:21 ` __write alias missing on arm platforms Sebastian Gottschall
2015-10-22 20:55   ` Rich Felker
2015-10-22 21:18     ` Sebastian Gottschall [this message]
2015-10-22 21:26       ` Szabolcs Nagy
2015-11-05 12:38         ` Szabolcs Nagy

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=562952BE.7030501@dd-wrt.com \
    --to=s.gottschall@dd-wrt.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).