Mailing List Archive: Small bug in gpgme configure script or Makefile ?!?

Small bug in gpgme configure script or Makefile ?!?

Jul 27, 2004, 2:28 AM

Post #1 of 4 (1960 views)

When I try to configure && make gpgme 0.3.12 from source from the following
directory:
/data/tmp/GnuPG 1.9/gpgme-0.3.12

I get this error from make

(cd .libs/libgpgme.lax/libassuan.al && ar x /data/tmp/GnuPG
1.9/gpgme-0.3.12/gpgme/../assuan/.libs/libassuan.al)
ar: /data/tmp/GnuPG: No such file or directory
make[3]: *** [libgpgme.la] Error 9
make[3]: Leaving directory `/data/tmp/GnuPG 1.9/gpgme-0.3.12/gpgme'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/data/tmp/GnuPG 1.9/gpgme-0.3.12/gpgme'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/data/tmp/GnuPG 1.9/gpgme-0.3.12'
make: *** [all] Error 2

It seems that the Makefile doesn't like the path with the source code to
contain a directory name with a blank. It works fine when I change the
directory from
/data/tmp/GnuPG 1.9/gpgme-0.3.12
to
/data/tmp/GnuPG/gpgme-0.3.12

I noticed the same problem with another component of the GnuPG software
collection. It's probably just a problem with using quotes the wrong way in
the autoconf or automake input files.

Re: Small bug in gpgme configure script or Makefile ?!? [ In reply to ]

wk at gnupg

Jul 27, 2004, 3:27 AM

Post #2 of 4 (1915 views)

Permalink

On Tue, 27 Jul 2004 11:28:30 +0200, bsmaillist said:

> I noticed the same problem with another component of the GnuPG software
> collection. It's probably just a problem with using quotes the wrong way in
> the autoconf or automake input files.

Likely. However you should use 0.3.16 and not any of the older gpgme
versions.

Werner

Re: Small bug in gpgme configure script or Makefile ?!? [ In reply to ]

bsmaillist at skynet

Jul 27, 2004, 4:44 AM

Post #3 of 4 (1914 views)

Permalink

On Tuesday 27 July 2004 12:27, Werner Koch wrote:
> On Tue, 27 Jul 2004 11:28:30 +0200, bsmaillist said:
> > I noticed the same problem with another component of the GnuPG software
> > collection. It's probably just a problem with using quotes the wrong way
> > in the autoconf or automake input files.
>
> Likely. However you should use 0.3.16 and not any of the older gpgme
> versions.
>
>
> Werner
>
>
> _______________________________________________
> Gpa-dev mailing list
> Gpa-dev@gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gpa-dev

It is the same with gpgme v0.3.16.

Re: Small bug in gpgme configure script or Makefile ?!? [ In reply to ]

marcus.brinkmann at ruhr-uni-bochum

Jul 28, 2004, 4:29 AM

Post #4 of 4 (1921 views)

Permalink

At Tue, 27 Jul 2004 11:28:30 +0200,
bsmaillist@skynet.be wrote:
> When I try to configure && make gpgme 0.3.12 from source from the following
> directory:
> /data/tmp/GnuPG 1.9/gpgme-0.3.12

[You reported this to be true for 0.3.16, too]

> I get this error from make
>
> (cd .libs/libgpgme.lax/libassuan.al && ar x /data/tmp/GnuPG
> 1.9/gpgme-0.3.12/gpgme/../assuan/.libs/libassuan.al)
> ar: /data/tmp/GnuPG: No such file or directory

[...]

> It seems that the Makefile doesn't like the path with the source code to
> contain a directory name with a blank.

Note that the above Makefile snippet is provided by one of the
auto-tools (automake or libtool, I guess). If you really want to fix
that for 0.3.x, you'd have to address this with those tools and then
regenerate the Makefiles.

I just tried to use a source path with a space, and it worked for the
CVS version. However, the build procedure changed, so I can't tell if
this means the bug is fixed in latest auto tools, and anyway I can't
tell you if the latest auto tools work for the 0.3.x branch without
changes.

Thanks,
Marcus