unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Germán Arias" <german@xelalug.org>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: "Mark H Weaver" <mhw@netris.org>,
	"Ludovic Courtès" <ludo@gnu.org>,
	guile-user@gnu.org
Subject: Re: Problems to install Guile 2.0.0
Date: Wed, 09 Mar 2011 19:44:37 -0600	[thread overview]
Message-ID: <1299721477.6397.4.camel@german-desktop> (raw)
In-Reply-To: <878vwoko32.fsf@ossau.uklinux.net>

OK, I solved the problem. Checking the files vm.c, vm.s,... . I found
the character

\f

at file vm.c. I remember some time ago I had a compilation problem
caused by this character in a file. However, this character not always
cause problems. I removed all occurrences of this character in vm.c, and
that was the solution :)  Thank you all for your help.


On mié, 2011-03-09 at 20:58 +0000, Neil Jerram wrote:
> Germán Arias <german@xelalug.org> writes:
> 
> > Output for gcc --version:
> >
> > german@german-desktop:~$ gcc --version
> > gcc (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu3)
> > Copyright (C) 2007 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions.  There is
> > NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > PURPOSE.
> 
> Hi Germán,
> 
> Just in case it's not already obvious to you, the thing that's really
> weird here is that compilation apparently fails but without displaying
> any kind of detailed error message.  This is practically unheard of, and
> I don't recall any similar case in previous Guile-related reports.
> 
> That's why we're all asking questions - which may seem strange to you -
> about your exact compiler, platform and so on.
> 
> So, basically, if there's anything you can do to get the compiler to
> print more information about why it is failing, that would help.
> 
> Regards,
>         Neil




  reply	other threads:[~2011-03-10  1:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 18:57 Problems to install Guile 2.0.0 Germán Arias
2011-03-08 22:02 ` Ludovic Courtès
2011-03-08 23:54   ` Germán Arias
2011-03-09  1:21     ` Mark H Weaver
2011-03-09  4:50       ` Germán Arias
2011-03-09  5:10         ` Mark H Weaver
2011-03-09  6:42           ` Germán Arias
2011-03-09  8:52             ` Mark H Weaver
2011-03-09 20:42               ` Germán Arias
2011-03-09 20:58                 ` Neil Jerram
2011-03-10  1:44                   ` Germán Arias [this message]
2011-03-10 10:58                     ` Ludovic Courtès
2011-03-10 14:24                       ` rixed
2011-03-10 18:25                       ` Keith Wright
2011-03-10 18:30                         ` Ludovic Courtès
2011-03-08 22:12 ` Mark H Weaver
2011-03-09  0:05   ` Germán Arias
2011-03-09  8:19     ` Andy Wingo
  -- strict thread matches above, loose matches on Subject: below --
2011-03-10 18:41 Mike Gran
2011-03-10 19:02 ` Germán Arias
2011-03-10 19:46   ` Mark H Weaver

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=1299721477.6397.4.camel@german-desktop \
    --to=german@xelalug.org \
    --cc=guile-user@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.org \
    --cc=neil@ossau.uklinux.net \
    /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).