From: James Bergstra <james.bergstra@umontreal.ca>
Cc: bug-guile@gnu.org
Subject: Re: 1.8 build problem
Date: Wed, 3 May 2006 01:53:35 -0400 [thread overview]
Message-ID: <20060503055334.GA30105@aphex.iro.umontreal.ca> (raw)
In-Reply-To: <20060501193558.GG12707@aphex.iro.umontreal.ca>
> I'm on Fedora core, AMD64, with guile 1.6 already installed in /usr/bin, the
> compiler is gcc 4.2.0. I want to install guile 1.8 in my account, so I
>
> 1. download the 1.8 tgz
> 2. issue ./configure --prefix=~/pub/64 (no problem)
> 3. issue make. no problem during compiling... then... it hangs. So I kill it,
> and reissue make. It hangs again, after printing the following text:
....
>
> what's up with that?
In case anybody cares, this problem disappeared when I used gcc 3.2 instead.
--
james bergstra
http://www-etud.iro.umontreal.ca/~bergstrj
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-05-03 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 19:35 1.8 build problem James Bergstra
2006-05-03 5:53 ` James Bergstra [this message]
2006-05-03 6:25 ` James Bergstra
2006-05-04 15:59 ` Neil Jerram
2006-05-03 18:13 ` Neil Jerram
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=20060503055334.GA30105@aphex.iro.umontreal.ca \
--to=james.bergstra@umontreal.ca \
--cc=bug-guile@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).