On Tuesday 01 January 2008 15:03:03 DJ Delorie wrote:
> > Please check that you don't have a stale guile-config executable in your
> > $PATH.
>
> No guile-config.  I removed guile-dev again to test...
>
> "make config" gives repeated errors like this:
>
> checking for XML::Parser... ok
> ./configure: line 28704: GUILE_FLAGS: command not found
> checking Guile version >= 1.6.0... info: No menu item `guileversion' in
> node `(dir)Top'.
>
> ./configure: line 28720: test: 1: unary operator expected
> ./configure: line 28721: test: 6: unary operator expected
> checking whether scm_c_catch is declared... no
>
> But does NOT fail.

Are you building from tarballs, or from git?

It looks like you are building from git, using autogen.sh to generate 
configure.  Autoconf *cannot generate configure correctly* without the Guile 
development package installed, because the necessary M4 macros aren't 
available, and the nature of M4 means that there is no way to detect whether 
M4 macros are missing.

What happens then is that, as your log indicates, the GUILE_FLAGS macro is not 
expanded. It is then picked up as a missing command by the shell.

If, on the other hand, you build from tarballs, pre-built configure scripts 
are provided.  In this case, configure will have a correctly-expanded 
GUILE_FLAGS macro, and will correctly report Guile as not being installed.

People compiling the git version need to check manually that they install the 
right development packages.  People building from tarballs get some help from 
configure.  This is the way it is with every autotools-based package I have 
used.

The next question will be to ask: why we don't check autoconf-generated files 
into git?  There's a very simple answer to that.  What sort of patch is 
easier to audit: a one-line change to a Makefile.am, or that plus several 
pages of diff automatically generated by automake as a result of that 
one-line change?

I hope that clarifies the reason for your difficulties.  Of course, if you 
want to avoid all of this hassle, you could just use the Fedora packages:

  yum install geda-\*

                                      Peter

-- 
Peter Brett

Electronic Systems Engineer
Integral Informatics Ltd

Attachment: signature.asc
Description: This is a digitally signed message part.


_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev

Reply via email to