unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Jan Schukat <shookie@email.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 13848@debbugs.gnu.org
Subject: bug#13848: Statically linking guile-2.0.
Date: Tue, 05 Mar 2013 16:44:55 +0100	[thread overview]
Message-ID: <513612F7.90002@email.de> (raw)
In-Reply-To: <87vc96i1st.fsf@gnu.org>

Ok, tried that on linux.

autoreconf demanded automake 1.12, which isn't available via .debs on 
ubuntu yet, so I installed that from the sources.

after that I get this error message:

configure.ac:873: warning: macro 'AM_GNU_GETTEXT' not found in library
autoreconf: running: /usr/bin/autoconf --force
configure.ac:900: error: possibly undefined macro: AM_GNU_GETTEXT
       If this token and others are legitimate, please use m4_pattern_allow.
       See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1

I simply don't know enough about automake internals to even know where 
to begin to go about such errors. What library would such macros be 
defined in? And if I knew that, would I even want to do any changes 
there? Or is that generated from one of the dozens of scripts in the 
auto toolchain? I wouldn't even know where one might apply that 
m4_pattern_allow. What I can gather it could also just be a sign of a 
syntax error in the configure.ac.

Regards

Jan Schukat

On 03/05/2013 11:22 AM, Ludovic Courtès wrote:
> Hi,
>
> Sorry for the delay.
>
> Jan Schukat <shookie@email.de> skribis:
>
>> ice-9/boot-9.scm:106:20: In procedure #<procedure a434b00 at
>> ice-9/boot-9.scm:97:6 (thrown-k . args)>:
>> ice-9/boot-9.scm:106:20: In procedure dynamic-pointer: Symbol not
>> found: scm_init_popen
>> make[3]: *** [ice-9/popen.go] Error 1
> I see: the (ice-9 popen) module depends on functionality that is missing
> when building with --disable-posix, so it cannot be built.  This is a
> bug: Guile shouldn’t try to build ice-9/popen.scm when --disable-posix
> is used.
>
> Regarding file names on MinGW, Andy Wingo did a lot of work recently to
> integrate them correctly.  This will be in Guile 2.0.8, but in the
> meantime could you try building Guile’s ‘stable-2.0’ branch from Git?
>
>    git clone git://git.sv.gnu.org/guile.git
>    git checkout stable-2.0
>    autoreconf -vfi
>    ./configure
>    make && make check
>
> Thanks in advance,
> Ludo’.






  reply	other threads:[~2013-03-05 15:44 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 16:19 bug#13848: Statically linking guile-2.0 Jan Schukat
2013-03-02 15:28 ` Ludovic Courtès
2013-03-03 23:20   ` Jan Schukat
2013-03-05  0:54   ` Jan Schukat
2013-03-05 10:22     ` Ludovic Courtès
2013-03-05 15:44       ` Jan Schukat [this message]
2013-03-05 17:25         ` Ludovic Courtès
2013-03-05 22:25           ` Jan Schukat
2013-03-06 23:12             ` Ludovic Courtès
2013-03-09 13:44               ` Jan Schukat
2013-03-09 23:06                 ` Andy Wingo
2013-03-09 23:57                   ` shookie
2013-03-10  4:09                   ` shookie
2013-03-10 17:32                     ` Andy Wingo
2013-03-10 18:54                       ` shookie
2013-03-10 19:23                       ` Andy Wingo
2013-03-10 21:17                         ` shookie
2013-03-10 22:03                         ` shookie
2013-03-10 22:53                           ` Andy Wingo
2013-03-11  0:07                             ` shookie
2013-03-11  1:43                             ` shookie
2013-03-11  8:26                               ` Andy Wingo
2013-03-11  9:30                                 ` shookie
2013-03-13  9:30                                   ` Andy Wingo
2013-03-13 19:04                                     ` bug#13848: Aw: " Jan Schukat
2013-03-16  1:36                                     ` Jan Schukat
2013-03-29 19:35                                       ` Ludovic Courtès
2013-03-30  0:20                                         ` Jan Schukat
2013-03-30 21:27                                           ` Ludovic Courtès
2013-04-05 23:14                                             ` Jan Schukat
2013-04-07 10:20                                               ` Ludovic Courtès
2013-04-07 16:20                                                 ` bug#13848: Aw: " Jan Schukat
2013-04-07 18:22                                                   ` Andy Wingo
2013-04-07 19:18                                                     ` bug#13848: Aw: " Jan Schukat
2013-04-07 20:00                                                       ` Ludovic Courtès
2013-04-07 21:06                                                         ` bug#13848: Aw: " Jan Schukat
2013-04-08  7:48                                                           ` Ludovic Courtès
2013-03-10 17:38                   ` shookie
2013-03-10 17:38                   ` shookie
2013-03-14 13:54                   ` Ludovic Courtès
2013-03-09  9:32 ` Andy Wingo
2013-03-09 15:42   ` Jan Schukat

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=513612F7.90002@email.de \
    --to=shookie@email.de \
    --cc=13848@debbugs.gnu.org \
    --cc=ludo@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).