From: Didier Godefroy <ldg@ulysium.net>
To: Mike Gran <spk121@yahoo.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>,
"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Building guile 1.8.6 on Tru64 5.1b
Date: Sat, 25 Apr 2009 16:19:35 +0200 [thread overview]
Message-ID: <C618E897.2829A%ldg@ulysium.net> (raw)
In-Reply-To: <1240665855.3133.197.camel@localhost.localdomain>
on 4/25/09 3:24 PM, Mike Gran at spk121@yahoo.com uttered the following:
> On Sat, 2009-04-25 at 14:29 +0200, Didier Godefroy wrote:
>>> http://git.savannah.gnu.org/cgit/guile.git/log/?h=branch_release-1-8
>>
>> I simply removed that @LTLIBINTL@ from that Makefile and re-ran the make to
>> allow the build to be successful then I ran the tests, and the numbers.test
>> does fail. However I still went ahead with the install, hoping it wouldn't
>> bother my build of autogen. I tried with autogen 5.5.7 and now 5.9.7 and get
>> the same errors of unresolved symbols scm_makstr and gh_eval_str which seem
>> to be guile related. I couldn't find anything useful to fix this while
>> googling, so I'm back to the guile list.
> Those two functions do exist in Guile 1.8.6, but, they may not get built
> in if you configured with the --disable-deprecated option.
>
> So, if you've been building guile with ./configure --disable-deprecated,
> then that is your problem. If that isn't it, then you could try
> explicitly enabling them by using ./configure --enable-deprecated.
That worked!!! Geez! That was so simple and I found no such info by
googling. Hopefully this time being on the mailing list someone with this
same issue will find that info.
One small detail though, the detected version of guile is 1.4 but what I
built should be showing something like 1.8.6 right?
Trying to build autogen again now, the configure finally succeeded.
--
Didier Godefroy
mailto:dg@ulysium.net
next prev parent reply other threads:[~2009-04-25 14:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 20:23 Building guile 1.8.6 on Tru64 5.1b Didier Godefroy
2009-04-18 22:43 ` Ludovic Courtès
2009-04-19 9:04 ` Didier Godefroy
2009-04-21 13:59 ` Didier Godefroy
2009-04-21 14:10 ` Linas Vepstas
2009-04-21 15:19 ` Ludovic Courtès
2009-04-21 18:35 ` Didier Godefroy
2009-04-21 19:00 ` Ludovic Courtès
2009-04-21 19:37 ` Didier Godefroy
2009-04-21 20:40 ` Ludovic Courtès
2009-04-21 15:14 ` Ludovic Courtès
2009-04-21 18:25 ` Didier Godefroy
2009-04-21 18:47 ` Didier Godefroy
2009-04-21 19:07 ` Ludovic Courtès
2009-04-21 19:46 ` Didier Godefroy
2009-04-21 20:41 ` Ludovic Courtès
2009-04-21 20:53 ` Didier Godefroy
2009-04-21 22:55 ` Ludovic Courtès
2009-04-22 8:11 ` Didier Godefroy
2009-04-22 8:23 ` Didier Godefroy
2009-04-22 9:27 ` Ludovic Courtès
2009-04-22 14:39 ` Didier Godefroy
2009-04-23 22:49 ` Ludovic Courtès
2009-04-25 12:29 ` Didier Godefroy
2009-04-25 13:24 ` Mike Gran
2009-04-25 14:19 ` Didier Godefroy [this message]
2009-04-21 20:25 ` Didier Godefroy
2009-04-21 20:50 ` Ludovic Courtès
2009-04-21 20:58 ` Didier Godefroy
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=C618E897.2829A%ldg@ulysium.net \
--to=ldg@ulysium.net \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
--cc=spk121@yahoo.com \
/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).