unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Barry Fishman <barry@ecubist.org>
To: guile-user@gnu.org
Subject: Re: getting started writing desktop applications
Date: Thu, 21 Jul 2016 17:39:47 -0400	[thread overview]
Message-ID: <m3h9bir7q4.fsf@ecube.ecubist.org> (raw)
In-Reply-To: 20160721163556.1f00d52b@capac


On 2016-07-21 16:35:56 +03, David Pirotte wrote:
>> The whole autoreconf setup for added modules seems to get broken with
>> every development releases.  Some packages seem to require multiple
>> reconfigs before they build. 
>
> I'm not aware of any of this, could you be more specific?

OK. Looking at guile-dbi  My install script ended up including:

--8<---------------cut here---------------start------------->8---
if [ ! -f configure ]; then
  echo ";;; Doing first autogen.sh"
  ./autogen.sh --no-configure
  echo ";;; Doing autoreconf"
  autoreconf -fi
  echo ";;; Doing second autogen.sh"
  ./autogen.sh --no-configure
fi
echo ";;; Now configure"
configure --prefix="${dest}" \
  LDFLAGS='-L/usr/lib64/mysql' \
  CPPFLAGS="-I${dest}/include"
--8<---------------cut here---------------end--------------->8---

I don't know it that is still needed, but fragile build environment lead
to cargo cult behavior.  And its never completely clear what the autogen
autoconf autotool (or whatever it should be called) environment is
doing.

>
>> Tests break with errors like not being able to exec "/bin/sh"
>
> This is the symptom that you have a 'corrupted' environment, and the
> test suite can't
> find guile and/or guild

> This has been fixed, patched under revision: they will be pushed and
> guile-lib will
> be released by the end of this month.
>
> 	https://lists.gnu.org/archive/html/guile-devel/2016-07/msg00055.html

Since you don't explain the symptoms of the bug, I don't know if it
what I am experiencing.

When I try to "make check" guile-lib (from the git repository) I get:

--8<---------------cut here---------------start------------->8---
make  check-TESTS
make[2]: Entering directory '/home2/barry/src/gen/guile-lib/unit-tests'
make[3]: Entering directory '/home2/barry/src/gen/guile-lib/unit-tests'
Backtrace:
           2 (primitive-load "/bin/sh")
In ice-9/eval.scm:
   223:20  1 (proc #<directory (guile-user) 128af30>)
In unknown file:
           0 (%resolve-variable (7 . #) #<directory (guile-user) 128?>)
--8<---------------cut here---------------end--------------->8---

In the test code I see:

   (primitive-load (getenv "DOC_GUILE_LIBRARY_SCM"))

And in the Makefile:

   DOC_GUILE_LIBRARY_SCM=$(top_srcdir)/doc/guile-library.scm 

And:

   top_srcdir=..

so I don't know where the "/bin/sh" could be coming from.

--
Barry Fishman




  reply	other threads:[~2016-07-21 21:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-17 16:38 getting started writing desktop applications Christopher M. Hobbs
2016-07-17 16:43 ` Paul Emsley
2016-07-18  4:52   ` Nala Ginrut
2016-07-20 16:01     ` Barry Fishman
2016-07-21 19:35       ` David Pirotte
2016-07-21 21:39         ` Barry Fishman [this message]
2016-07-21 23:15           ` David Pirotte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3h9bir7q4.fsf@ecube.ecubist.org \
    --to=barry@ecubist.org \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).