similar to: [Bug 3707] New: Build failure on musl in ssh_systemd_notify (port-linux.c:369:25: error: passing argument 2 of 'connect' from incompatible pointer type)

https://bugzilla.mindrot.org/show_bug.cgi?id=3708 Bug ID: 3708 Summary: Tracking bug for OpenSSH 9.9 Product: Portable OpenSSH Version: -current Hardware: Other OS: All Status: NEW Keywords: meta Severity: enhancement Priority: P5 Component: Miscellaneous Assignee:

I don't think we should attempt to mangle symbols declared in assembly source files. If you're writing assembly, you will need to handle ABI portability, including the _ prefix on win32 x86. clang will run the C preprocessor for you if you use the .S file suffix (case matters). On Tue, Oct 22, 2013 at 7:08 AM, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com>wrote: > For example, I

For example, I execute the following command sequences: H:\CI\bld\compilers\musl\src\math\i386>type sqrt.s #.globl _sqrt .global sqrt #.type sqrt, at function #_sqrt: sqrt: fldl 4(%esp) fsqrt fstsw %ax sub $12,%esp fld %st(0) fstpt (%esp) mov (%esp),%ecx and $0x7ff,%ecx cmp $0x400,%ecx jnz 1f and $0x200,%eax

2013/10/23 Reid Kleckner <rnk at google.com> > I don't think we should attempt to mangle symbols declared in assembly > source files. If you're writing assembly, you will need to handle ABI > Sorry for the unclear statements, I didn't means the assembler to mangle symbols declared in assembly source files, I means directly use assembly directive to choice which symbol

I'm trying to do a standalone build of Opus and I get the following messages when compiling for android arm64 using clang:   CC       silk/fixed/arm/warped_autocorrelation_FIX_neon_intr.lo silk/fixed/arm/warped_autocorrelation_FIX_neon_intr.c:43:37: warning: incompatible pointer types assigning to 'const long *' from 'long long *' [-Wincompatible-pointer-types]    

Looks like commit 05a8c47b9be8a6b8ffc091eab461fece9d40dcd0 (tests: Test all calls through multiple layers of filters and a plugin.) introduced an issue. $ git clean -dxf && autoreconf -i && ./configure && make ... in.Tpo -c -o test_layers_plugin_la-test-layers-plugin.lo `test -f 'test-layers-plugin.c' || echo './'`test-layers-plugin.c libtool: compile: gcc

> ELLCC (http://ellcc.org), my clang/LLVM based cross development tool chain for > ARM, Microblaze, Mips, Power PC, and X86, now incorporates musl > (http://www.etalabs.net/musl) as its standard C library for Linux. musl is a > MIT licensed, highly POSIX compliant library offering high performance and a > small foot print. I spent several weeks evaluating musl before deciding to use

ELLCC (http://ellcc.org), my clang/LLVM based cross development tool chain for ARM, Microblaze, Mips, Power PC, and X86, now incorporates musl (http://www.etalabs.net/musl) as its standard C library for Linux. musl is a MIT licensed, highly POSIX compliant library offering high performance and a small foot print. I spent several weeks evaluating musl before deciding to use it in ELLCC. The

>>>>> Alba Pompeo <albapompeo at gmail.com> >>>>> on Mon, 1 Feb 2016 15:33:11 -0200 writes: > Here's what I did. > svn checkout https://svn.r-project.org/R/trunk/ > cd ./trunk > aclocal -I m4 && autoconf > tools/rsync-recommended > cd .. > mkdir build > cd build > ../trunk/configure

Hi, I?m trying to compile libguestfs on Alpine Linux, that uses musl libc (lightweight, fast and simple standards-conformance libc). It fails in the check phase due to missing glibc-style extended printf formatters. -- checking for register_printf_specifier... no checking for register_printf_function... no configure: error: in `/tmp/libguestfs/src/libguestfs-1.32.6?: configure: error: No support

Hello, I wanted to ask if there's a reason efi/wrapper.{h,c} use __uint*_t instead of including stdint.h and using the therein defined uint*_t types? This breaks compilation of the efi blobs on systems with the musl libc since that doesn't define __uint*_t types. -- Simon Thelen

Hi, I've updated the musl version of the clang/LLVM based ELLCC compiler suite to use musl release 0.9.14. As usual the musl guys have been doing a great job. The new release looks great! http://ellcc.org I've also started to port libunwind into ELLCC. That's the last step for a fully non-gnu run-time environment: libcxx/libcxxabi/libunwind/musl/compiler-rt for C and C++ under

On Thu, Feb 04, 2016 at 04:35:22PM -0200, Alba Pompeo wrote: > I forwarded our talk on musl mailing list to R mailing list. > I got this response. > Does it help? > Also, what do you think about making a new email that's sent to both > musl and R mailing list, that way devs from both projects can > communicate? It's a tad inefficient for me to keep forwarding messages

It is setting TZ and using tzset(). R is not multi-threaded so it is safe. Simon figure out the important settings from the config.log and config.h files on a musl system: /* #undef USE_INTERNAL_MKTIME */ #define HAVE_TM_GMTOFF 1 #define HAVE_TM_ZONE 1 Does this help anyone debug the issue? Simon just went on vacation. On Thu, Feb 4, 2016 at 7:32 PM, Rich Felker <dalias at libc.org>

https://bugzilla.samba.org/show_bug.cgi?id=10715 Summary: IPv6 configure test fails on musl c-library Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: timo.teras at iki.fi

https://bugzilla.mindrot.org/show_bug.cgi?id=2274 Bug ID: 2274 Summary: Build fixes for musl libc Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs at mindrot.org

https://bugzilla.netfilter.org/show_bug.cgi?id=1278 Bug ID: 1278 Summary: FTBFS on musl due to missing include Product: ulogd Version: SVN (please provide timestamp) Hardware: x86_64 OS: other Status: NEW Severity: critical Priority: P5 Component: ulogd Assignee:

Commit-ID: e3e5ce11c99ce4e5638df44ed87661945a241632 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=e3e5ce11c99ce4e5638df44ed87661945a241632 Author: Baruch Siach <baruch at tkos.co.il> AuthorDate: Fri, 2 Mar 2018 08:32:16 +0200 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] histedit: fix build with musl

Commit-ID: a2020fbd897e3c3d41c75294f4e43a0e07487822 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=a2020fbd897e3c3d41c75294f4e43a0e07487822 Author: Baruch Siach <baruch at tkos.co.il> AuthorDate: Fri, 2 Mar 2018 08:32:16 +0200 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: histedit: fix build with

> Hello, > > I wanted to ask if there's a reason efi/wrapper.{h,c} use __uint*_t > instead of including stdint.h and using the therein defined uint*_t > types? This breaks compilation of the efi blobs on systems with the musl > libc since that doesn't define __uint*_t types. > > -- > Simon Thelen FWIW... As a simple quick basic test, I took the efi32