Intention to adopt eudev

Boian Bonev bbonev at ipacct.com
Wed Sep 15 02:55:00 BST 2021


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi Jesse,

On Tue, 2021-09-14 at 21:27 -0300, Jesse Smith wrote:
> 
> > > The error I get when trying to run the autogen.sh script is:
> > 
> > > libtoolize: linking file 'm4/lt~obsolete.m4'
> > > configure.ac:164: error: possibly undefined macro: AC_DEFINE
> > >       If this token and others are legitimate, please use
> > > m4_pattern_allow.
> > >       See the Autoconf documentation.
> > > autoreconf: /usr/bin/autoconf failed with exit status: 1
> > 
> 
> 
> I fund the issue. I was missing the package "python-pkgconfig". Once
> that was installed, the autogen.sh script ran fine. Turned out someone
> else had the same problem and published a solution. That got me through
> the autogen script and then I had to install gperf to get the configure
> script to complete.

Sorry for not being helpful before you found it. Here is the Devuan package
control file:

https://git.devuan.org/devuan/eudev/src/branch/suites/unstable/debian/control

The complete list of things needed for a proper build are:

Build-Depends: debhelper-compat (= 12),
               dpkg-dev (>= 1.17.14),
               pkg-config,
               docbook-xsl,
               docbook-xml,
               m4,
               automake (>= 1.13),
               autoconf (>= 2.63),
               intltool,
               gperf,
               gnu-efi [amd64 i386 arm64],
               libcap-dev (>= 1:2.24-9~),
               libselinux1-dev (>= 2.1.9),
               libacl1-dev,
               libkmod-dev (>= 15),
               libblkid-dev (>= 2.25),
               gobject-introspection,
               libglib-object-introspection-perl,
               xsltproc

Please note that on Debian and derivatives the builds do not depend on what is
installed on the build system. Normally they happen in a clean chroot with a
minimal system, then the build dependencies are installed and then the build is
performed.

I didn't test but I suppose that python-pkgconfig pulls pkg-config and for the
build to succeed only the later is needed, not the former.

> I'll write up some rough BUILD instructions, including the tools I had
> to add to get eudev to compile and share them. Maybe it'll make the
> process just a little smoother for other newcomers.

Please file a pull request at https://github.com/eudev-project/eudev
GPG signed commit(s) would be preferred.


With best regards,
b.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEumC8IPN+WURNbSUAE2VyCRPS8i0FAmFBUnQACgkQE2VyCRPS
8i3YAA//ZUaC8yEquYWhRMwL44VG3IbFX8lHapOHde64JY6FQs2+ns1xapaUMvkK
0wBPjLBc/rKOhBznRtVlOax/wzMMQivGZ0gicYW8dNEveo8vcW7vxfDW7KWb48ok
QmaB3dzmKqytq+oC+M1oRggEqZ63Ncw2XsRISyKgLXxYF1jTmRqYRgCD3EDw5Sw6
7FQ5AI0H38L09YfHPvKesR2CU9zIq9pt1/1ME/lSs+FdTD8u40HM1Zsa8H8vRpfR
7zXez/mfPbnmEHxDGqPu8IjN/ClodkKi2mWdGHJbE9uGXRYVDiBcJQ6oSZNE/Q5I
9TPbmSFTimzreqaZQ+ZkmTDE5gpmq5FXX/LPSZWM9d6/ZVwZb9EOP9WdisOa48X7
B3+gIBRe90XX8kHt65AsScjv+VMx5da45zvlpq2kuzykYfov4WBGRjpCjMJwzYfy
/td6uD8V0rUEtV1dsNO2nDIDYFWrg3hIRA4JW7DMM46us1zApXTUg+0ORX5pO8N5
ypDmoYOT91um+b1DPvKi21w6WxymEj8J9SgCOjj35Br9GcAbRKFHT6CDvreI5YiM
QLslEPPtxgjafV7FTTceUjMyL62V6TiOaVzgVIdIUiHXZ/DCUzNmXE7GnghKcBBL
P7ZCPQlFiM8KkL4FyENK+sc46xonyHc8k9p/ZFNbpj78JtvQARg=
=diYz
-----END PGP SIGNATURE-----




More information about the Debian-init-diversity mailing list