Compiling from GIT

Compiling from GIT

[Hans Aberg]

I made a new system installation, and now the GIT version does not generate 'configure'. I thought one should just run ./autogen.sh; however, this fails, because autoconf (called via autoreconf in this script) cannot find gettext.m4, which is in /usr/local/share/aclocal/, which should be copied into ./m4/.

I can't see if it is a problem with Guile's configure.ac or some installation problem with autoconf-2.68 that makes it not looking into /usr/local/share.

Re: Compiling from GIT

[Andy Wingo]

On Wed 09 Feb 2011 11:40, Hans Aberg <haberg-1@telia.com> writes:

> I made a new system installation, and now the GIT version does not
> generate 'configure'. I thought one should just run ./autogen.sh;
> however, this fails, because autoconf (called via autoreconf in this
> script) cannot find gettext.m4, which is in /usr/local/share/aclocal/,
> which should be copied into ./m4/.

Sounds like you're installing things to multiple prefixes (/usr and
/usr/local in your case, presumably).

> I can't see if it is a problem with Guile's configure.ac or some
> installation problem with autoconf-2.68 that makes it not looking into
> /usr/local/share.

autoconf will look in /usr/local iff it is installed to /usr/local,
iirc.

Andy
-- 
http://wingolog.org/

Re: Compiling from GIT

[Hans Aberg]

On 9 Feb 2011, at 21:01, Andy Wingo wrote:

>> I made a new system installation, and now the GIT version does not
>> generate 'configure'. I thought one should just run ./autogen.sh;
>> however, this fails, because autoconf (called via autoreconf in this
>> script) cannot find gettext.m4, which is in /usr/local/share/aclocal/,
>> which should be copied into ./m4/.
> 
> Sounds like you're installing things to multiple prefixes (/usr and
> /usr/local in your case, presumably).

I'm on Mac OS X, so originally, there is no /usr/local/, but packages that one takes down, compiled using ./configure && make, typically ends up there.

>> I can't see if it is a problem with Guile's configure.ac or some
>> installation problem with autoconf-2.68 that makes it not looking into
>> /usr/local/share.
> 
> autoconf will look in /usr/local iff it is installed to /usr/local,
> iirc.


There is one
  $ /usr/bin/autoconf --version
  autoconf (GNU Autoconf) 2.61
and I installed
  $ /usr/local/bin/autoconf --version
  autoconf (GNU Autoconf) 2.68
The ./autogen.sh script writes the version number, so it is clear that the latter is being called.

However, it uses /usr/share/aclocal/, not /usr/local/share/aclocal/. I can see that by changing the name of the former - it still does not work. But if I in addition set a symbolic link to the latter, then it works.

Re: Compiling from GIT

[Hans Aberg]

> However, it uses /usr/share/aclocal/, not /usr/local/share/aclocal/. I can see that by changing the name of the former - it still does not work. But if I in addition set a symbolic link to the latter, then it works.

That is, I get the compiler internal segmentation fault mentioned before. Latest version that compiled is guile-1.9.13; 1.9.14 produced an error; and 1.9.15 also gets the segmentation fault. I filed a bug report to Apple, but it will probably not be fixe anytime soon, I would gather.

Re: Compiling from GIT

[Andy Wingo]

On Wed 09 Feb 2011 23:57, Hans Aberg <haberg-1@telia.com> writes:

>> However, it uses /usr/share/aclocal/, not /usr/local/share/aclocal/. I
> can see that by changing the name of the former - it still does not
> work. But if I in addition set a symbolic link to the latter, then it
> works.
>
> That is, I get the compiler internal segmentation fault mentioned
> before. Latest version that compiled is guile-1.9.13; 1.9.14 produced an
> error; and 1.9.15 also gets the segmentation fault. I filed a bug report
> to Apple, but it will probably not be fixe anytime soon, I would gather.

Are you using CC=gcc-4.2 ?

Andy
-- 
http://wingolog.org/

Re: Compiling from GIT

[Hans Aberg]

On 10 Feb 2011, at 09:40, Andy Wingo wrote:

>>> However, it uses /usr/share/aclocal/, not /usr/local/share/aclocal/. I
>> can see that by changing the name of the former - it still does not
>> work. But if I in addition set a symbolic link to the latter, then it
>> works.
>> 
>> That is, I get the compiler internal segmentation fault mentioned
>> before. Latest version that compiled is guile-1.9.13; 1.9.14 produced an
>> error; and 1.9.15 also gets the segmentation fault. I filed a bug report
>> to Apple, but it will probably not be fixe anytime soon, I would gather.
> 
> Are you using CC=gcc-4.2 ?


$ gcc --version
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5664)

Re: Compiling from GIT

[Hans Aberg]

When compiling guile from GIT or guile-1.9.1, libguile/Makefile just writes
  CC     libguile_2.0_la-vm.lo
What commands are processed? - For the compiler internal segmentation fault bugreport, I need to modify the gcc arguments (also getting the preprocessed vm.c).

Re: Compiling from GIT

[Andy Wingo]

On Sat 12 Feb 2011 12:30, Hans Aberg <haberg-1@telia.com> writes:

> When compiling guile from GIT or guile-1.9.1, libguile/Makefile just
> writes
>   CC     libguile_2.0_la-vm.lo
> What commands are processed? - For the compiler internal segmentation
> fault bugreport, I need to modify the gcc arguments (also getting the
> preprocessed vm.c).

`make V=1'.  See "silent-rules" in the automake manual.

Andy
-- 
http://wingolog.org/

Re: Compiling from GIT

[Hans Aberg]

On 12 Feb 2011, at 13:02, Andy Wingo wrote:

>> When compiling guile from GIT or guile-1.9.1, libguile/Makefile just
>> writes
>>  CC     libguile_2.0_la-vm.lo
>> What commands are processed? - For the compiler internal segmentation
>> fault bugreport, I need to modify the gcc arguments (also getting the
>> preprocessed vm.c).
> 
> `make V=1'.  See "silent-rules" in the automake manual.

This worked. Thanks.

Re: Compiling from GIT

[Hans Aberg]

On 9 Feb 2011, at 21:01, Andy Wingo wrote:

> On Wed 09 Feb 2011 11:40, Hans Aberg <haberg-1@telia.com> writes:
> 
>> I made a new system installation, and now the GIT version does not
>> generate 'configure'. I thought one should just run ./autogen.sh;
>> however, this fails, because autoconf (called via autoreconf in this
>> script) cannot find gettext.m4, which is in /usr/local/share/aclocal/,
>> which should be copied into ./m4/.
> 
> Sounds like you're installing things to multiple prefixes (/usr and
> /usr/local in your case, presumably).
> 
>> I can't see if it is a problem with Guile's configure.ac or some
>> installation problem with autoconf-2.68 that makes it not looking into
>> /usr/local/share.
> 
> autoconf will look in /usr/local iff it is installed to /usr/local,
> iirc.

It turns out that one must install automake too, which contains aclocal - otherwise the one in /usr/bin will be chosen, and it will chose files without /usr/local. Then it works as it should, modulo that gcc internal segmentation fault.

Compiling from GIT

[Hans Aberg]

> I made a new system installation, and now the GIT version does not generate 'configure'. I thought one should just run ./autogen.sh; however, this fails, because autoconf (called via autoreconf in this script) cannot find gettext.m4, which is in /usr/local/share/aclocal/, which should be copied into ./m4/.

I was able to fix this problem by copying the files to m4 (cp /usr/local/share/aclocal/* m4/). For some reason, autoconf does not copy them.

However, when compiling it, and also guile-1.9.15, I get segmentation fault (as below) in the compiler (Mac OS X 10.6.6 x86-64 Xcode 3.2.5). This does not happen in a somewhat older guile-1.9.8.

  Hans


libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -DBUILDING_LIBGUILE=1 -I.. -I.. -I../lib -I../lib -I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include -I/usr/local/include -D_THREAD_SAFE -Wall -Wmissing-prototypes -Wdeclaration-after-statement -Wundef -Wswitch-enum -fvisibility=hidden -I/usr/local/include -g -O2 -MT libguile_2.0_la-vm.lo -MD -MP -MF .deps/libguile_2.0_la-vm.Tpo -c vm.c  -fno-common -DPIC -o .libs/libguile_2.0_la-vm.o
vm.c:907: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://developer.apple.com/bugreporter> for instructions.
make[3]: *** [libguile_2.0_la-vm.lo] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Re: Compiling from GIT

[Andy Wingo]

On Wed 09 Feb 2011 19:39, Hans Aberg <haberg-1@telia.com> writes:

> vm.c:907: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://developer.apple.com/bugreporter> for instructions.

Please bring this up with your OS vendor; it is not a Guile bug.

Thanks,

Andy
-- 
http://wingolog.org/

Re: Compiling from GIT

[Hans Aberg]

On 10 Feb 2011, at 17:50, Andy Wingo wrote:

>> vm.c:907: internal compiler error: Segmentation fault
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <URL:http://developer.apple.com/bugreporter> for instructions.
> 
> Please bring this up with your OS vendor; it is not a Guile bug.

Already done yesterday; I mentioned it to you earlier today.

It might though be a GCC bug, but they are at 4.5.2 now.

  Hans

Re: Compiling from GIT

[Ludovic Courtès]

Hans Aberg <haberg-1@telia.com> writes:

> On 10 Feb 2011, at 17:50, Andy Wingo wrote:
>
>>> vm.c:907: internal compiler error: Segmentation fault
>>> Please submit a full bug report,
>>> with preprocessed source if appropriate.
>>> See <URL:http://developer.apple.com/bugreporter> for instructions.
>> 
>> Please bring this up with your OS vendor; it is not a Guile bug.
>
> Already done yesterday; I mentioned it to you earlier today.
>
> It might though be a GCC bug, but they are at 4.5.2 now.

Despite the name, etc., this is *not* GCC; it is Apple CC.

Thanks,
Ludo’.

Re: Compiling from GIT

[Hans Aberg]

On 10 Feb 2011, at 23:16, Ludovic Courtès wrote:

>>>> vm.c:907: internal compiler error: Segmentation fault
>>>> Please submit a full bug report,
>>>> with preprocessed source if appropriate.
>>>> See <URL:http://developer.apple.com/bugreporter> for instructions.
>>> 
>>> Please bring this up with your OS vendor; it is not a Guile bug.
>> 
>> Already done yesterday; I mentioned it to you earlier today.
>> 
>> It might though be a GCC bug, but they are at 4.5.2 now.
> 
> Despite the name, etc., this is *not* GCC; it is Apple CC.

It is even mentioned in the GCC manual. But I wondered if the bug is due to Apple or the original GCC.

Re: Compiling from GIT

[Hans Aberg]

On 10 Feb 2011, at 23:16, Ludovic Courtès wrote:

>>>> vm.c:907: internal compiler error: Segmentation fault
>>>> Please submit a full bug report,
>>>> with preprocessed source if appropriate.
>>>> See <URL:http://developer.apple.com/bugreporter> for instructions.
>>> 
>>> Please bring this up with your OS vendor; it is not a Guile bug.
>> 
>> Already done yesterday; I mentioned it to you earlier today.
>> 
>> It might though be a GCC bug, but they are at 4.5.2 now.
> 
> Despite the name, etc., this is *not* GCC; it is Apple CC.

Apple is changing from a GCC derivation in Xcode 3 and earlier, which are for free, to LLVM in Xcode 4, which they now charge money for. So perhaps they have removed all GPLed software.

Hans