After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 795901 - Failed autogen on Fedora 28
Failed autogen on Fedora 28
Status: RESOLVED INCOMPLETE
Product: GEGL
Classification: Other
Component: core
git master
Other Linux
: Normal normal
: ---
Assigned To: Default Gegl Component Owner
Default Gegl Component Owner
Depends on:
Blocks:
 
 
Reported: 2018-05-08 03:02 UTC by Dov Grobgeld
Modified: 2018-05-09 13:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
autogen.sh failure log (10.56 KB, text/plain)
2018-05-08 03:02 UTC, Dov Grobgeld
  Details
build: Abort as soon as autoreconf fails (787 bytes, patch)
2018-05-09 13:10 UTC, Debarshi Ray
committed Details | Review

Description Dov Grobgeld 2018-05-08 03:02:36 UTC
Created attachment 371787 [details]
autogen.sh failure log

I just checked out the master branch on a fedora28 system and ran ./autogen.sh which failed with the following error:

config.status: error: cannot find input file: `Makefile.in'

See log file for details.
Comment 1 Debarshi Ray 2018-05-09 12:55:10 UTC
The relevant part of the log seems to be:

autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:185: installing '../compile'
configure.ac:549: error: required file '../config.rpath' not found
configure.ac:144: installing '../missing'
bin/Makefile.am: installing '../depcomp'
autoreconf: automake failed with exit status: 1
Comment 2 Dov Grobgeld 2018-05-09 12:57:53 UTC
@debarshi: Agree. But it would also make sense for ./autogen.sh to fail with an error and not run configure if automake fails.
Comment 3 Debarshi Ray 2018-05-09 13:03:31 UTC
I believe that you need the gettext-devel package, because:

$ rpm -qf /usr/share/gettext/config.rpath 
gettext-devel-0.19.8.1-12.fc27.x86_64
$
Comment 4 Debarshi Ray 2018-05-09 13:10:47 UTC
Created attachment 371841 [details] [review]
build: Abort as soon as autoreconf fails
Comment 5 Debarshi Ray 2018-05-09 13:14:01 UTC
(In reply to Debarshi Ray from comment #3)
> I believe that you need the gettext-devel package, because:
> 
> $ rpm -qf /usr/share/gettext/config.rpath 
> gettext-devel-0.19.8.1-12.fc27.x86_64
> $

I see that it managed to find autopoint, which comes from the same package. Do have a separate set of Autotools components in a non-system prefix?
Comment 6 Dov Grobgeld 2018-05-09 13:22:16 UTC
Strange. I reran it again, and now it worked. gettext-devel was already installed... Perhaps it was some path or environment variable problem? Don't know. Anyhow, thanks for the help. I'm closing the bug.
Comment 7 Debarshi Ray 2018-05-09 13:22:49 UTC
Comment on attachment 371841 [details] [review]
build: Abort as soon as autoreconf fails

Pushed to master.

Distcheck continues to pass; and the build fails as expected if bits of gettext are missing, but I didn't test the specific case where autopoint is present but config.rpath is missing.