Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#810589: use of sys/cdefs and musl libc

54 views
Skip to first unread message

Vincent Bernat

unread,
Jan 10, 2016, 3:20:03 AM1/10/16
to
Package: libbsd-dev
Version: 0.8.1-1
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi!

I was trying to compile a program using libbsd with musl-gcc/musl-ldd
and got the following error:

In file included from /usr/include/bsd/string.h:36:0,
from ../../../src/compat/strlcpy.c:21:
/usr/include/bsd/sys/cdefs.h:28:28: fatal error: sys/cdefs.h: No such file or directory

The musl FAQ says:

Congratulations, you have found a bug! The bug is in the application
that uses this internal glibc header. This header is *not* intended
to be used by any program. File a bug report.

http://wiki.musl-libc.org/wiki/FAQ#Q:_I.27m_trying_to_compile_something_against_musl_and_I_get_error_messages_about_sys.2Fcdefs.h

So, filing a bug report, but I suppose this is not as simple as
that. :)

- -- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (101, 'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libbsd-dev depends on:
ii libbsd0 0.8.1-1

libbsd-dev recommends no packages.

libbsd-dev suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJWkg6mAAoJEJWkL+g1NSX5AX0QAIMi1wpr0dFuaNmmwC45oxZp
Jf/X1pjPrW0oRl+cu9nxKO4L1QFwM8bgOTW5abdd9CzFymTKpCphw+VMA5ZvPo1q
RUTcqLtsskAQ3EPGC68gg8ad3pZ+eSTJOZ8AL3LmaG/8BLFOMewDJzUthXKISUlV
1koyB+KcRcSkVvUAbzb61t9tVbNh+tkMSIqct9AuW9hKeWs2pYUv633L912XU9GK
+soHLvECFTdm+WodQzNp8MLPxsOEaIlQnpJPdkR8zIR4Z8P85JC3g9D+0IkltLrA
fjVwJmKsSSoGJaKWcaQlK40RA9gxlkpcxPcqkwRuqTdN+XOGo9ugyuJS5SbOw/cz
4FxHxMrFKRFNq1b64WUVTzRVaAUW1KrjgKhLhCNyoWkSMzLo6c69bZXetEYdD3QT
Bf/fwW+fslcYE71n19j2Muurn6g9ChiK7qOasnRiImYFdIGkJOaEGZY8HyZ1wJ+k
hb4I0P3ksoOmhndf3hm/wvFsVE/0NMaSmWLbMyoiUZoCTr8HBlEl35BwwqPgR9pR
Dph6JF1pvIAWqAEWRuGOmhmF9sQJZiIi7fQ3FOWVO2cRx1ifw01tofpVgTaYqKfv
VuH9NVcKp/pHO0qf5b2S+qMtub30d1W1Y0rBWE2rDJAIDkes3HOlpDDg5jIgp+kS
+oiU9pcsO69Iu7VIAZCP
=mEOJ
-----END PGP SIGNATURE-----

Vincent Bernat

unread,
Jan 10, 2016, 3:40:02 AM1/10/16
to
❦ 10 janvier 2016 08:56 +0100, Vincent Bernat <ber...@debian.org> :

> I was trying to compile a program using libbsd with musl-gcc/musl-ldd
> and got the following error:
>
> In file included from /usr/include/bsd/string.h:36:0,
> from ../../../src/compat/strlcpy.c:21:
> /usr/include/bsd/sys/cdefs.h:28:28: fatal error: sys/cdefs.h: No such file or directory
>
> The musl FAQ says:
>
> Congratulations, you have found a bug! The bug is in the application
> that uses this internal glibc header. This header is *not* intended
> to be used by any program. File a bug report.
>
> http://wiki.musl-libc.org/wiki/FAQ#Q:_I.27m_trying_to_compile_something_against_musl_and_I_get_error_messages_about_sys.2Fcdefs.h
>
> So, filing a bug report, but I suppose this is not as simple as
> that. :)

Note that even if this "bug" wasn't here, I wouldn't be able to directly
use libbsd since it needs to be compiled for musl libc first. So, feel
free to just ignore the bug as I won't go further either.
--
Use library functions.
- The Elements of Programming Style (Kernighan & Plauger)
signature.asc
0 new messages