| Summary: | %configure fails because %__libtoolize isn't defined anymore | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jani Välimaa <jani.valimaa> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpm-4.15.0-0.rc1.5.mga8 | CVE: | |
| Status comment: | |||
| Attachments: | Build log | ||
Created attachment 11278 [details]
Build log
__libtoolize was removed in upstream commmit https://github.com/rpm-software-management/rpm/commit/9f486b3 Assigning to you, Thierry, for 'rpm'. Assignee:
bugsquad =>
thierry.vignaud Fixed in rpm-mageia-setup-2.41 (though we could live without that dumb macro...) Resolution:
(none) =>
FIXED |
Javapackages-tools build failed in BS because %configure macro is used. %configure macro is broken because %__libtoolize isn't defined anymore. %configure sets _legacy_autotools to 1 and calls %main_configure %main configure calls %__libtoolize_configure and it's empty if %__libtoolize isn't defined. %__libtoolize_configure %{?__libtoolize:(cd $CONFIGURE_TOP; [ ! -f configure.in -a ! -f configure.ac ] || %{__libtoolize} --copy --force)} All this causes plain ; to be inserted to build script and it causes failure. I think we should define __libtoolize again and/or ensure that %__libtoolize_configure returns something even when %__libtoolize isn't defined. Perhaps append %{?!__libtoolize:true} to it?