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 682579 - libgsf autogen.sh fails non-sourcedir build
libgsf autogen.sh fails non-sourcedir build
Status: RESOLVED FIXED
Product: libgsf
Classification: Core
Component: General
1.14.x
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks: 569778
 
 
Reported: 2012-08-24 01:58 UTC by Theppitak Karoonboonyanan
Modified: 2012-09-07 22:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Get rid of `pwd` from ACLOCAL_INCLUDE (752 bytes, patch)
2012-08-24 02:02 UTC, Theppitak Karoonboonyanan
none Details | Review
Calculate absolute srcdir (876 bytes, patch)
2012-08-25 07:27 UTC, Theppitak Karoonboonyanan
none Details | Review

Description Theppitak Karoonboonyanan 2012-08-24 01:58:20 UTC
When building libgsf using JHBuild with buildroot set to different one from checkoutroot, it fails at configure stage with the following message:

---8<---
/home/thep/vcs/gnome_git/libgsf/autogen.sh --prefix /home/gnome3 --libdir '/home/gnome3/lib64' --without-bonobo --without-gnome-vfs --disable-static --disable-gtk-doc --disable-silent-rules 
checking for autoconf >= 2.54...
  testing autoconf2.50... found 2.69
checking for automake >= 1.8...
  testing automake-1.12... not found.
  testing automake-1.11... found 1.11.6
checking for libtool >= 1.4.3...
  testing libtoolize... found 2.4.2
checking for glib-gettext >= 2.2.0...
  testing glib-gettextize... /home/gnome3/bin/glib-gettextize: line 74: echo: write error: Broken pipe
/home/gnome3/bin/glib-gettextize: line 75: echo: write error: Broken pipe
found 2.33.11
checking for intltool >= 0.25...
  testing intltoolize... found 0.50.2
checking for pkg-config >= 0.14.0...
  testing pkg-config... found 0.26
checking for gtk-doc >= 1.0...
  testing gtkdocize... found 1.18.1
Checking for required M4 macros...
Checking for forbidden M4 macros...
Processing /home/thep/vcs/gnome_git/libgsf/configure.in
Running libtoolize...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
Running glib-gettextize... Ignore non-fatal messages.
Copying file mkinstalldirs
Copying file po/Makefile.in.in

Please add the files
  codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
  progtest.m4
from the /home/gnome3/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.

Running intltoolize...
Running gtkdocize...
Running aclocal-1.11...
aclocal-1.11: couldn't open directory '/home/thep/build/gnome_git/libgsf//home/thep/vcs/gnome_git/libgsf/m4': No such file or directory
---8<---
Comment 1 Theppitak Karoonboonyanan 2012-08-24 02:02:04 UTC
Created attachment 222274 [details] [review]
Get rid of `pwd` from ACLOCAL_INCLUDE

Get rid of `pwd` from ACLOCAL_INCLUDE, which caused duplicated prefix to $srcdir. $srcdir should already represent the source dir itself.
Comment 2 Morten Welinder 2012-08-25 01:13:13 UTC
"pwd" has been there for ~6 years.

I looks like it is used there is a poor-man's trick to make the
path absolute.  Your patch fails to do that.  I don't know what
kind of trouble that will cause.
Comment 3 Theppitak Karoonboonyanan 2012-08-25 06:49:08 UTC
(In reply to comment #2)
> "pwd" has been there for ~6 years.
> 
> I looks like it is used there is a poor-man's trick to make the
> path absolute.  Your patch fails to do that.  I don't know what
> kind of trouble that will cause.

The problem of "pwd" trick is that it assumes $srcdir to be relative path, which is not the case for me. And the problem of my patch is also the assumption on absolute $srcdir. Either one fails.

So, we may need something like `cd $srcdir/m4 && pwd` instead.
Comment 4 Theppitak Karoonboonyanan 2012-08-25 07:27:49 UTC
Created attachment 222378 [details] [review]
Calculate absolute srcdir
Comment 5 Morten Welinder 2012-09-07 22:21:47 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.