[bug #31963] guile-config: inconsistent behaviour when run using lilypond configure under meta/uninstalled-env bash or fully install

[bug #31963] guile-config: inconsistent behaviour when run using lilypond configure under meta/uninstalled-env bash or fully install

[Ian Hulin]

URL:
  <http://savannah.gnu.org/bugs/?31963>

                 Summary: guile-config: inconsistent behaviour when run using
lilypond configure under meta/uninstalled-env bash or fully install
                 Project: Guile
            Submitted by: ian_hulin
            Submitted on: Thu Dec 23 22:01:21 2010
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Hi all,

If we run lilypond ./configure under meta/uninstalled-env bash on a machine
where 1.8.7 is installed it hangs
as follows:

ian@nanny-ogg:~/lily-build-g2$ /home/ian/lilypond/configure
--srcdir=/home/ian/lilypond --disable-optimising --prefix=/usr/local
checking build system type... i686-pc-linux-gnu
<snip>
checking for working metafont mode... ljfour
checking for kpsewhich... kpsewhich
checking for guile-config... guile-config

If I run exactly the same configuration in a Virtual Machine with guile
configured, compiled and installed the configuration runs to completion.


ian@greebo:~/lily-build-g2$ /home/ian/lilypond/configure
--srcdir=/home/ian/lilypond --disable-optimising --prefix=/usr/local
checking build system type... i686-pc-linux-gnu
<snip>

checking for guile-config... guile-config
checking guile-config version... 1.9.14
checking guile compile flags... -pthread -I/usr/local/include/guile/2.0
<snip>
configure: creating ./config.status
config.status: creating config.make
config.status: creating config.hh

Type:
    make all       to build LilyPond
    make install   to install LilyPond
    make help      to see all possible targets

Edit local.make for local Makefile overrides.
ian@greebo:~/lily-build-g2$

It's really tedious having to keep a full VM or laptop installation set
up to work around this inconsistency, is there any chance of fixing this
in the guile kit, please?  If not, how can we work around this in our
configure?

I think this has been the behaviour since Guile V1.9.11.

Cheers,

Ian Hulin






    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31963>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/

[bug #31963] guile-config: inconsistent behaviour when run using lilypond configure under meta/uninstalled-env bash or fully install

[Andy Wingo]

Follow-up Comment #1, bug #31963 (project guile):

Ian, did you happen to have a stale "guile-config" binary around in Guile's
$abs_top_builddir?  At some point it switched from being there to being in
meta/, but you could have been left with a stale build product.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31963>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/

Re: [bug #31963] guile-config: inconsistent behaviour when run using lilypond configure under meta/uninstalled-env bash or fully install

[Ian Hulin]

On 13/02/11 18:43, Andy Wingo wrote:
> Follow-up Comment #1, bug #31963 (project guile):
> 
> Ian, did you happen to have a stale "guile-config" binary around in Guile's
> $abs_top_builddir?  At some point it switched from being there to being in
> meta/, but you could have been left with a stale build product.
> 
It's possible.  I've generally downloaded guile into separate
directories and built from that directory, but in this environment(my
main machine) I did have a fit of enthusiasm and did a complete
installation of a much earlier version of guile (I think 1.9.11) all the
way through to running make install.  I then backed out using make
uninstall.

Could this have left crud hanging around to cause the observed effects?
 I've been working around it using either a Virtual Machine environment
or my laptop where I've never installed anything before 1.9.14.

How could I check the $abs_top_builddir setting for you?

As I've got a work-round please don't let this hold up the Guile release.

Cheers,
Ian