[gentoo-dev] Re: autotools

[Samuel Bernardo]

Thank you Michal and Haelwenn for your advises.

I'm taking as reference the documentation about functions syntax in
devmanual[1] (very useful for a quickly review).

In the source code where autoreconf is being called I found a
configure.ac and Makefile.am.

Looking into autogen.sh[2] script prvided by the maintainer I confirm
that he runs the following commands:

- autoreconf -i -f

- for each supported distribution defines variable extra_opts

- "${SRC_DIR}/configure" --enable-maintainer-mode --prefix=/usr
$extra_opts "$@"

So it seems that the best approach would be the way you suggested in
your example Haelwenn.

[1] https://devmanual.gentoo.org/eclass-reference/ebuild/index.html

[2] https://github.com/snapcore/snapd/blob/master/cmd/autogen.sh




signature.asc
Description: OpenPGP digital signature

[gentoo-dev] Re: autotools

[Michal Prívozník]

On 26. 3. 2020 18:47, Samuel Bernardo wrote:
> Dear all,
> 
> I send this email to ask you for your help for the better approach to
> translate the following autoreconf command to an ebuild:
> 
>> |autoreconf -i -f ./configure \ --prefix=/usr \
>> --libexecdir=/usr/lib/snapd \
>> --with-snap-mount-dir=/var/lib/snapd/snap \ --enable-apparmor \
>> --enable-nvidia-biarch \ --enable-merged-usr|
> I realise that eautoreconf from autotools.eclass doesn't accept any
> parameters, so how would you advise me to reproduce it inside an ebuild
> using the available functions and eclasses?
> 
> My goal is to create an ebuild from latest snapd pkgbuild:
> 
> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=snapd
> 
> Thank you,
> 
> Samuel
> 

I guess you are not really after autoreconf arguments rather than
./configure ones. You want to focus on src_configure() in the ebuild. I
suggest starting here:


https://devmanual.gentoo.org/ebuild-writing/functions/src_configure/configuring/index.html

and there are plenty of examples existing in the portage. You will need
to define USE flags for your ebuild though so that users can
enable/disable parts of functionality.

Happy hacking!

Michal

[gentoo-dev] Re: autotools - 'make' infinite loop

[Marcus Furlong]

Finally, this was caused by a missing one-liner Makefile.am, it was already
fixed upstream but didn't make it into the tarball. Thanks anyway for the
suggestions.

Marcus,

-- 
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Re: autotools - 'make' infinite loop

[Marcus Furlong]

Diego 'Flameeyes' Pettenò wrote:

 On Wednesday 05 July 2006 22:05, Marcus Furlong wrote:
 Running 'configure' goes fine, but running 'make' just keeps running
 configure over and over.
 It's commonly caused when the timestamp of configure and the sources for
 configure are messed up. Make sure no file has modification time in the
 future, and let the configure script to be regenerated forcefully before
 make.

Ok, I tried this. I checked the timestamps of all files, and they're all in
the past. I deleted configure and let it be regenerated anyway, but the
same thing happened as before. :(

 If you're using kde eclass, just remove the 'configure' file before
 kde_src_compile, and the eclass will take care.

Tried this too, and no luck.

 If the files have modification time in the future, you must run in
 src_unpack something like
 
 find ${S} -type f -print0 | xargs -0 touch

Even trying to 'configure' and run 'make' outside of an ebuild does not
work, that's why I'm guessing it's some sort of misconfiguration with
autotools. I'll gladly try any other suggestions that anyone has!

Marcus.

-- 
gentoo-dev@gentoo.org mailing list