[Bug guile/19149] Message when guile is required but not available is not clear

[Bug guile/19149] Message when guile is required but not available is not clear

[xdje42 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19149

Doug Evans <xdje42 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xdje42 at gmail dot com

--- Comment #1 from Doug Evans <xdje42 at gmail dot com> ---
Hmmm, are you sure that gdb was built without guile support?
Note that if you elide mentioning guile (either with --with-guile[=foo] or
--without-guile) then configure will look for a locally available copy.

gdb should not be printing that message at all if guile support is not
configured in.

What's the output of
gdb --batch -ex 'show config'
?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug guile/19149] Message when guile is required but not available is not clear

[yuri at tsoft dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19149

--- Comment #2 from yuri at tsoft dot com ---
FreeBSD port has an option "GUILE", which causes --with-guile to be passed.

With GUILE=on configure gets --with-guile parameter:
> --program-suffix=710  --enable-targets=all --enable-64-bit-bfd  --with-gdb-datadir=/usr/local/share/gdb710  --with-separate-debug-dir=/usr/lib/debug    --without-libunwind-ia64 --without-expat --with-guile --with-python=/usr/local/bin/python2.7 --enable-tui --with-system-readline --prefix=/usr/local ${_LATE_CONFIGURE_ARGS}

With GUILE=off configure doesn't get --with-guile parameter:
> --program-suffix=710  --enable-targets=all --enable-64-bit-bfd  --with-gdb-datadir=/usr/local/share/gdb710  --with-separate-debug-dir=/usr/lib/debug    --without-libunwind-ia64 --without-expat --with-python=/usr/local/bin/python2.7 --enable-tui --with-system-readline --prefix=/usr/local ${_LATE_CONFIGURE_ARGS}

However, the command you suggested still shows it is compiled with guile, even
though this flag wasn't passed by port:
> $ gdb --batch -ex 'show config'
>
> This GDB was configured as follows:
>    configure --host=x86_64-portbld-freebsd10.2 --target=x86_64-portbld-freebsd10.2
>              --with-auto-load-dir=:${prefix}/share/auto-load
>              --with-auto-load-safe-path=:${prefix}/share/auto-load
>              --without-expat
>              --with-gdb-datadir=/usr/local/share/gdb710 (relocatable)
>              --with-jit-reader-dir=/usr/local/lib/gdb (relocatable)
>              --without-libunwind-ia64
>              --with-lzma
>              --with-python=/usr/local (relocatable)
>              --with-guile
>              --with-separate-debug-dir=/usr/lib/debug
>              --without-babeltrace

-- and the OP problem occurs in this case (GUILE=off, no --with-guile to
configure).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug guile/19149] Message when guile is required but not available is not clear

[yuri at tsoft dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19149

--- Comment #4 from yuri at tsoft dot com ---
> The default value for --with-guile is "auto"

This means that once I have guile installed it shouldn't matter if --with-guile
option is present or not, but the actual behavior differs. It does work with an
option, and produces the OP message without it.

Now I am trying to make the port to be able to cleanly disable guile with
--with-guile=off, but configure fails:

> checking whether python supports threads... yes
> checking whether to use guile... off
> checking for pkg-config... /usr/local/bin/pkg-config
> checking for usable guile from /usr/local/bin/pkg-config... configure: error: unable to find usable guile version from "off"
> Makefile:8070: recipe for target 'configure-gdb' failed
> gmake[3]: *** [configure-gdb] Error 1

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug guile/19149] Message when guile is required but not available is not clear

[xdje42 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19149

--- Comment #5 from Doug Evans <xdje42 at gmail dot com> ---
>This means that once I have guile installed it shouldn't matter if --with-guile >option is present or not, but the actual behavior differs. It does work with an >option, and produces the OP message without it.

Not sure why that happens.
In the case where you are explicitly specifying --with-guile,
are you passing it an argument, as in "--with-guile=foo",
or are you passing it as just "--with-guile" ?

>Now I am trying to make the port to be able to cleanly disable guile with --with-guile=off, but configure fails:
>
>> checking whether python supports threads... yes
>> checking whether to use guile... off
>> checking for pkg-config... /usr/local/bin/pkg-config
>> checking for usable guile from /usr/local/bin/pkg-config... configure: error: >unable to find usable guile version from "off"
>> Makefile:8070: recipe for target 'configure-gdb' failed
>> gmake[3]: *** [configure-gdb] Error 1

Bleah.
My bad, it's spelled --with-guile=no or --without-guile.
grep for with-guile in gdb/configure.ac

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug guile/19149] Message when guile is required but not available is not clear

[yuri at tsoft dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19149

--- Comment #6 from yuri at tsoft dot com ---
For GUILE=on it passes "--with-guile". So the problem is that when there is no
such option passed, the assumed --with-guile=auto in the presence of guile
installation causes the message (from OP). It is supposed to behave the same
way as --with-guile in such case.
You might want to look why does this happen.

But now I fixed the FreeBSD port by adding --without-guile as per your
suggestion.
Here is the FreeBSD bug report for reference:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204041

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug guile/19149] Message when guile is required but not available is not clear

[xdje42 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19149

--- Comment #7 from Doug Evans <xdje42 at gmail dot com> ---
I may need some help looking into the difference, I can't recreate it here
(amd64-linux, fedora 21).

I'd be curious to see the contents of $build/gdb/Makefile and
$build/gdb/config.h
for the two cases (no --with-guile, with --with-guile).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug guile/19149] Message when guile is required but not available is not clear

[yuri at tsoft dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19149

--- Comment #8 from yuri at tsoft dot com ---
Created attachment 8746
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8746&action=edit
gdb/Makefile

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug guile/19149] Message when guile is required but not available is not clear

[yuri at tsoft dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19149

--- Comment #9 from yuri at tsoft dot com ---
Created attachment 8747
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8747&action=edit
gdb/config.h

The gdb/Makefile and gdb/config.h with and without the --with-guile option are
the same. Attaching them.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug guile/19149] Message when guile is required but not available is not clear

[yuri at tsoft dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19149

--- Comment #10 from yuri at tsoft dot com ---
Created attachment 8748
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8748&action=edit
Makefile different

Top-level Makefile has the difference though, attaching it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.