Failing to build g-wrap for guile 1.9.10

Failing to build g-wrap for guile 1.9.10

[Romel Sandoval]

Hello

I'm trying to build g-wrap downloaded with git for guile 1.9.10.

I have my guile on $HOME/usr. I also have the following environment
variables:

export LDFLAGS="-L$HOME/usr/lib"
export CPPFLAGS="-I$HOME/usr/include -I$HOME/usr/include/guile/2.0"
export PKG_CONFIG_PATH="$HOME/usr/lib/pkgconfig"
export LD_LIBRARY_PATH="$HOME/usr/lib/"
export PATH=$PATH:"$HOME/usr/bin"

When I try:

/autogen.sh --prefix $HOME/usr

It gives me:

{{{
DEBUG: /home/romel/usr
+ passing --prefix=/home/romel/usr to configure
+ options passed to configure:  --prefix=/home/romel/usr
+ check for build tools
  checking for autoconf >= 2.59 ... found 2.64, ok.
  checking for automake >= 1.5 ... found 1.11, ok.
  checking for libtoolize >= 1.4.0 ... found 2.2.6, ok.
+ creating m4/libchecks.m4
+ running libtoolize --copy --force...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in `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'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac
and
libtoolize: rerunning libtoolize, to keep the correct libtool macros
in-tree.
+ running aclocal -I m4 ...
+ running autoheader ...
+ running autoconf ...
+ running automake -a -c -Wno-portability...
configure.ac:37: installing `./config.guess'
configure.ac:37: installing `./config.sub'
configure.ac:5: installing `./install-sh'
configure.ac:5: installing `./missing'
doc/Makefile.am:1: installing `doc/texinfo.tex'
g-wrap/Makefile.am: installing `./depcomp'
+ running configure ... 
  ./configure default flags: --enable-maintainer-mode
  ./configure external flags:  --prefix=/home/romel/usr

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles...
yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for ranlib... ranlib
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1635000
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... (cached) ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking size of long... 8
checking whether byte ordering is bigendian... no
checking for working alloca.h... yes
checking for alloca... yes
checking for long long int... yes
checking for unsigned long long int... yes
checking for stdint.h... (cached) yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for EOVERFLOW... yes
checking for vasnprintf... no
checking for long double... yes
checking for wchar_t... yes
checking for wint_t... yes
checking for size_t... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for intmax_t... yes
checking for inline... inline
checking for alloca as a compiler built-in... yes
checking for stdint.h... (cached) yes
checking for SIZE_MAX... yes
checking absolute name of <stdint.h>... ///usr/include/stdint.h
checking whether stdint.h conforms to C99... yes
checking absolute name of <stdio.h>... ///usr/include/stdio.h
checking for ptrdiff_t... yes
checking for snprintf... yes
checking for wcslen... yes
checking for vasprintf... yes
checking whether <wchar.h> is standalone... yes
checking for stdint.h... (cached) yes
checking for alloca as a compiler built-in... (cached) yes
checking for vasprintf... (cached) yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBFFI... yes
checking size of size_t... 8
checking size of ssize_t... 8
/configure: line 13166: GUILE_PROGS: command not found
/configure: line 13167: GUILE_FLAGS: command not found
checking for guile-1.9... no
configure: Using 
/configure: line 13215: syntax error near unexpected token
`HAVE_SRFI_34,'
/configure: line 13215: `GUILE_MODULE_AVAILABLE(HAVE_SRFI_34, (srfi
srfi-34))'
  configure failed
}}}

Any idea why is this happening?

I have successfully build guile-dbi with this setup.

Please note that guile is not recognized.

Re: Failing to build g-wrap for guile 1.9.10

[Andy Wingo]

Hi Romel,

On Tue 01 Jun 2010 01:38, Romel Sandoval <romel@lavabit.com> writes:

> /configure: line 13215: `GUILE_MODULE_AVAILABLE(HAVE_SRFI_34, (srfi
> srfi-34))'
>   configure failed

It seems that aclocal is not finding guile.m4. Try running
ACLOCAL_FLAGS='-I/my/prefix/share/aclocal' ./autogen.sh.

Cheers,

Andy
-- 
http://wingolog.org/

Re: Failing to build g-wrap for guile 1.9.10

[Romel Sandoval]

OK, after setting ACLOCAL_FLAGS now configure script finish
successfully. But says that it's not working with guile 1.9. But I'm
using Guile 1.9.10:

..
checking size of size_t... 8
checking size of ssize_t... 8
checking for guile... /home/romel/usr/bin/guile
checking for guile-config... /home/romel/usr/bin/guile-config
checking for guile-tools... /home/romel/usr/bin/guile-tools
checking libguile compile flags... -I/home/romel/usr/include/guile/2.0
-I/home/romel/usr/include  
checking libguile link flags... -R/home/romel/usr/lib
-L/home/romel/usr/lib -lguile-2.0 -lgc -lunistring -lcrypt -lm -lltdl  
checking for guile-1.9... no   <-------------------------- LOOK AT THIS!
configure: Using /home/romel/usr/bin/guile
checking if (srfi srfi-34) is available... yes
checking if (srfi srfi-35) is available... yes
checking for GLIB... yes
configure: building GLib 2.0 support
checking whether gcc accepts -std=gnu99... yes
configure: creating ./config.status
config.status: creating Makefile
..

Could that represent a problem?

After configure while trying to build I got this:

..
Making all in g-wrap
make[2]: se ingresa al directorio `/home/romel/src/g-wrap/g-wrap'
make  all-am
make[3]: se ingresa al directorio `/home/romel/src/g-wrap/g-wrap'
/bin/bash ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
-I..  -I..  -I/home/romel/usr/include
-I/home/romel/usr/include/guile/2.0  -g -O2 -Wall -Wmissing-prototypes
-Werror -std=gnu99 -MT core-runtime.lo -MD -MP
-MF .deps/core-runtime.Tpo -c -o core-runtime.lo core-runtime.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I..
-I/home/romel/usr/include -I/home/romel/usr/include/guile/2.0 -g -O2
-Wall -Wmissing-prototypes -Werror -std=gnu99 -MT core-runtime.lo -MD
-MP -MF .deps/core-runtime.Tpo -c core-runtime.c  -fPIC -DPIC
-o .libs/core-runtime.o
cc1: warnings being treated as errors
core-runtime.c: In function ‘gw_raise_error’:
core-runtime.c:55: error: ignoring return value of ‘vasprintf’, declared
with attribute warn_unused_result
make[3]: *** [core-runtime.lo] Error 1
make[3]: se sale del directorio `/home/romel/src/g-wrap/g-wrap'
make[2]: *** [all] Error 2
make[2]: se sale del directorio `/home/romel/src/g-wrap/g-wrap'
make[1]: *** [all-recursive] Error 1
make[1]: se sale del directorio `/home/romel/src/g-wrap'
make: *** [all] Error 2

Thanks.

El mar, 01-06-2010 a las 11:20 +0200, Andy Wingo escribió:
> Hi Romel,
> 
> On Tue 01 Jun 2010 01:38, Romel Sandoval <romel@lavabit.com> writes:
> 
> > /configure: line 13215: `GUILE_MODULE_AVAILABLE(HAVE_SRFI_34, (srfi
> > srfi-34))'
> >   configure failed
> 
> It seems that aclocal is not finding guile.m4. Try running
> ='-I/my/prefix/share/aclocal' ./autogen.sh.
> 
> Cheers,
> 
> Andy

Re: Failing to build g-wrap for guile 1.9.10

[Ludovic Courtès]

Hi,

This won’t answer your question, but if you’re using 1.9, you may want
to look at the dynamic FFI in (system foreign) instead of G-Wrap.

Thanks,
Ludo’.

Re: Failing to build g-wrap for guile 1.9.10

[Andy Wingo]

On Tue 01 Jun 2010 20:44, Romel Sandoval <romel@lavabit.com> writes:

> checking for guile-1.9... no   <-------------------------- LOOK AT THIS!
>
> Could that represent a problem?

Hm, dunno. Perhaps it's looking for a binary with that name? It seems
you're building fine though.


> cc1: warnings being treated as errors
> core-runtime.c: In function ‘gw_raise_error’:
> core-runtime.c:55: error: ignoring return value of ‘vasprintf’, declared
> with attribute warn_unused_result

Here it seems you need to have configured with --disable-Werror,
unfortunately...

Andy
-- 
http://wingolog.org/

Re: Failing to build g-wrap for guile 1.9.10

[Andreas Rottmann]

[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]

Romel Sandoval <romel@lavabit.com> writes:

> After configure while trying to build I got this:
>
> ..
> Making all in g-wrap
> make[2]: se ingresa al directorio `/home/romel/src/g-wrap/g-wrap'
> make  all-am
> make[3]: se ingresa al directorio `/home/romel/src/g-wrap/g-wrap'
> /bin/bash ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I..  -I..  -I/home/romel/usr/include
> -I/home/romel/usr/include/guile/2.0  -g -O2 -Wall -Wmissing-prototypes
> -Werror -std=gnu99 -MT core-runtime.lo -MD -MP
> -MF .deps/core-runtime.Tpo -c -o core-runtime.lo core-runtime.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I..
> -I/home/romel/usr/include -I/home/romel/usr/include/guile/2.0 -g -O2
> -Wall -Wmissing-prototypes -Werror -std=gnu99 -MT core-runtime.lo -MD
> -MP -MF .deps/core-runtime.Tpo -c core-runtime.c  -fPIC -DPIC
> -o .libs/core-runtime.o
> cc1: warnings being treated as errors
> core-runtime.c: In function ‘gw_raise_error’:
> core-runtime.c:55: error: ignoring return value of ‘vasprintf’, declared
> with attribute warn_unused_result
>
Could you try the attached patch? It should fix this issue. As noted by
Andy Wingo, you can also use `--disable-Werror' when running configure.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: +vasprintf.patch --]
[-- Type: text/x-diff, Size: 1201 bytes --]

diff --git a/g-wrap/core-runtime.c b/g-wrap/core-runtime.c
index cb0f310..66c24a5 100644
--- a/g-wrap/core-runtime.c
+++ b/g-wrap/core-runtime.c
@@ -1,5 +1,5 @@
 /**********************************************************************
-Copyright (C) 2003-2004 Andreas Rottmann
+Copyright (C) 2003-2004, 2010 Andreas Rottmann
  
 This program is free software; you can redistribute it and/or modify
 it under the terms of the GNU Lesser General Public License as
@@ -50,15 +50,21 @@ gw_raise_error (GWLangArena arena, const char *proc, const char *fmt, ...)
 {
   char *message = NULL;
   va_list args;
-
+  int bytes_allocated;
+  
   va_start (args, fmt);
-  vasprintf (&message, fmt, args);
+  bytes_allocated = vasprintf (&message, fmt, args);
   va_end (args);
-  
-  gw_lang->raise_error (arena, proc, message);
-  
-  /* FIXME: we leak 'message' here, since this line won't be reached */
-  free (message);
+
+  if (bytes_allocated >= 0)
+  {
+    gw_lang->raise_error (arena, proc, message);
+    
+    /* FIXME: we leak 'message' here, since this line won't be reached */
+    free (message);
+  }
+  else
+    gw_lang->raise_error (arena, proc, "could not allocate error message");
 }
 
 void

[-- Attachment #3: Type: text/plain, Size: 63 bytes --]


Regards, Rotty
-- 
Andreas Rottmann -- <http://rotty.yi.org/>

Re: Failing to build g-wrap for guile 1.9.10

[Romel Sandoval]

I'm trying to build G-Wrap because guile-gnome depends on it.

El mié, 02-06-2010 a las 00:21 +0200, Ludovic Courtès escribió:
> Hi,
> 
> This won’t answer your question, but if you’re using 1.9, you may want
> to look at the dynamic FFI in (system foreign) instead of G-Wrap.
> 
> Thanks,
> Ludo’.

Re: Failing to build g-wrap for guile 1.9.10

[Romel Sandoval]

Well `--disable-Werror' make it. Thanks!

Rottmann, are you going to patch the code on the GIT repository?

El mié, 02-06-2010 a las 21:29 +0200, Andreas Rottmann escribió:
> Romel Sandoval <romel@lavabit.com> writes:
> 
> > After configure while trying to build I got this:
> >
> > ..
> > Making all in g-wrap
> > make[2]: se ingresa al directorio `/home/romel/src/g-wrap/g-wrap'
> > make  all-am
> > make[3]: se ingresa al directorio `/home/romel/src/g-wrap/g-wrap'
> > /bin/bash ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
> > -I..  -I..  -I/home/romel/usr/include
> > -I/home/romel/usr/include/guile/2.0  -g -O2 -Wall -Wmissing-prototypes
> > -Werror -std=gnu99 -MT core-runtime.lo -MD -MP
> > -MF .deps/core-runtime.Tpo -c -o core-runtime.lo core-runtime.c
> > libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I..
> > -I/home/romel/usr/include -I/home/romel/usr/include/guile/2.0 -g -O2
> > -Wall -Wmissing-prototypes -Werror -std=gnu99 -MT core-runtime.lo -MD
> > -MP -MF .deps/core-runtime.Tpo -c core-runtime.c  -fPIC -DPIC
> > -o .libs/core-runtime.o
> > cc1: warnings being treated as errors
> > core-runtime.c: In function ‘gw_raise_error’:
> > core-runtime.c:55: error: ignoring return value of ‘vasprintf’, declared
> > with attribute warn_unused_result
> >
> Could you try the attached patch? It should fix this issue. As noted by
> Andy Wingo, you can also use `--disable-Werror' when running configure.
> 
> Regards, Rotty

Re: Failing to build g-wrap for guile 1.9.10

[Andreas Rottmann]

Romel Sandoval <romel@lavabit.com> writes:

> Well `--disable-Werror' make it. Thanks!
>
> Rottmann, are you going to patch the code on the GIT repository?
>
Yes, I'm having a patch (the one in my last mail) in the queue, but I
can't reproduce the warning you encountered -- which version of GCC and
glibc did you use?

Regards, Rotty
-- 
Andreas Rottmann -- <http://rotty.yi.org/>

Re: Failing to build g-wrap for guile 1.9.10

[Romel Sandoval]

GCC 4.4.1
eglibc 2.10.1

El jue, 03-06-2010 a las 14:00 +0200, Andreas Rottmann escribió:
> Romel Sandoval <romel@lavabit.com> writes:
> 
> > Well `--disable-Werror' make it. Thanks!
> >
> > Rottmann, are you going to patch the code on the GIT repository?
> >
> Yes, I'm having a patch (the one in my last mail) in the queue, but I
> can't reproduce the warning you encountered -- which version of GCC and
> glibc did you use?
> 
> Regards, Rotty

Re: Failing to build g-wrap for guile 1.9.10

[Andreas Rottmann]

Romel Sandoval <romel@lavabit.com> writes:

> GCC 4.4.1
> eglibc 2.10.1
>
That's Debian sid, right? Strangely, I don't get the warning on current
sid.

Nevertheless, I've now pushed a patch that should fix the issue. Can you
confirm that building /without/ `--disable-Werror' works with current
g-wrap git?

Regards, Rotty
-- 
Andreas Rottmann -- <http://rotty.yi.org/>

Re: Failing to build g-wrap for guile 1.9.10

[Romel Sandoval]

My distro is Trisquel 3.5 based on Ubuntu.

I pulled the patch and now building works without --disable-Werror.

Regards,

Romel.

El jue, 03-06-2010 a las 16:36 +0200, Andreas Rottmann escribió:
> Romel Sandoval <romel@lavabit.com> writes:
> 
> > GCC 4.4.1
> > eglibc 2.10.1
> >
> That's Debian sid, right? Strangely, I don't get the warning on current
> sid.
> 
> Nevertheless, I've now pushed a patch that should fix the issue. Can you
> confirm that building /without/ `--disable-Werror' works with current
> g-wrap git?
> 
> Regards, Rotty