bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gprofng/29477] Build failure on musl: collector_module.h:78:13: err


From: slyich at gmail dot com
Subject: [Bug gprofng/29477] Build failure on musl: collector_module.h:78:13: error: duplicate member ‘pwrite’
Date: Fri, 02 Sep 2022 08:02:53 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=29477

--- Comment #4 from Sergei Trofimovich <slyich at gmail dot com> ---
Yeah, getting musl toolchain is trickier than glibc's. I suggest using a chroot
(or equivalent) of linux distribution that already supports it. I'm personally
using nixpkgs.

More conventional FHS-style distribution using musl would be adelie. Full
session to reproduce the failure there:

    # Get smallest rootfs from https://www.adelielinux.org/download/ (10MB),
    # unpack and and enter the chroot:
    $ mkdir /tmp/repro && cd /tmp/repro
    $ wget
https://distfiles.adelielinux.org/adelie/1.0/iso/rc2/adelie-rootfs-mini-x86_64-1.0-rc2.txz
    $ sudo tar xf adelie-rootfs-mini-x86_64-1.0-rc2.txz
    $ sudo systemd-nspawn --directory=.

    # Install bash (default shell is a bit clunky),
    # and build tools, fetch binutils and build it:
    $$ /sbin/apk add bash && bash
    $$ /sbin/apk add build-tools m4 bison flex gmp-dev texinfo
    $$ git clone --depth 1 https://sourceware.org/git/binutils-gdb.git
    $$ cd binutils-gdb/
    $$ ./configure && make
    ...
    In file included from dispatcher.c:35:
    /usr/include/sys/signal.h:1:2: warning: #warning redirecting incorrect
#include <sys/signal.h> to <signal.h> [-Wcpp]
     #warning redirecting incorrect #include <sys/signal.h> to <signal.h>
      ^~~~~~~
    In file included from dispatcher.c:30:
    ./../src/collector_module.h:78:13: error: duplicate member ‘pwrite’
       ssize_t (*pwrite64)();
                 ^~~~~~~~

It's a fully working basic c++ development environment:

    $$ printf "#include <iostream>\nint main() { std::cout << \"yay\" <<
std::endl; }" | g++ -x c++ - -o a && ./a
    yay

Hope that helps.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]