unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Michael Ellis <michael.f.ellis@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: Re: guile-2.0.0 build error on OS X 10.6.6
Date: Sun, 20 Feb 2011 18:23:05 -0500	[thread overview]
Message-ID: <AANLkTimJtLOtE75FExKfyWWaNNj3iwWkxd-8WtZLM-Jt@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=Hi815+jgJXJ7OwDxfzr+wYGAvHLP+_kyej9-m@mail.gmail.com>

On Sun, Feb 20, 2011 at 5:17 PM, Michael Ellis
<michael.f.ellis@gmail.com> wrote:
>  I don't have the config.log for gmp; it
> was installed some time ago.  I'll re-install it and either send you
> the flags or let you know in case that fixes the problem.

Reinstalling gmp made things slightly worse.  Building guile now fails
while compiling libibguile_2.0_la-vm.lo

Here's make output  for guile followed by the FLAGS in config.log for gmp.

Thanks,
Mike

bash-3.2$ make V=1
...
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H
-DBUILDING_LIBGUILE=1 -I.. -I.. -I../lib -I../lib
-I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include
-I/usr/local/include -D_THREAD_SAFE -Wall -Wmissing-prototypes
-Wdeclaration-after-statement -Wundef -Wswitch-enum
-fvisibility=hidden -I/usr/local/include -g -O2 -MT
libguile_2.0_la-vm.lo -MD -MP -MF .deps/libguile_2.0_la-vm.Tpo -c vm.c
-o libguile_2.0_la-vm.o >/dev/null 2>&1
make[3]: *** [libguile_2.0_la-vm.lo] Error 1

----------------------
FLAGS IN gmp/config.log
----------------------
bash-3.2$ cat config.log | grep FLAGS
CFLAGS=(unset)
CPPFLAGS=(unset)
CFLAGS=-O2 -pedantic -m64 -mtune=core2 -march=core2
CPPFLAGS=
GMP_LDFLAGS=
CXXFLAGS=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_YFLAGS_set=
ac_cv_env_YFLAGS_value=
ASMFLAGS=''
CFLAGS='-O2 -pedantic -m64 -mtune=core2 -march=core2'
CPPFLAGS=''
CXXFLAGS='-g -O2'
FFLAGS='-g -O2'
GMP_LDFLAGS=''
LDFLAGS=''
LIBGMPXX_LDFLAGS=''
LIBGMP_LDFLAGS=''
YFLAGS=''



  reply	other threads:[~2011-02-20 23:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-20 20:20 guile-2.0.0 build error on OS X 10.6.6 Michael Ellis
2011-02-20 21:37 ` Andy Wingo
2011-02-20 22:17   ` Michael Ellis
2011-02-20 23:23     ` Michael Ellis [this message]
2011-02-21  0:11     ` Hans Aberg
2011-02-21 14:21       ` Michael Ellis
2011-02-21 16:47         ` Hans Aberg
2011-02-21 17:03           ` Michael Ellis
2011-02-21 17:26             ` Hans Aberg
2011-02-21 17:34               ` Michael Ellis
2011-02-21 17:48                 ` Michael Ellis
2011-02-21 18:12                   ` Hans Aberg
2011-02-21 18:17                     ` Michael Ellis
2011-02-21 18:38                       ` Hans Aberg
2011-02-21 18:44                         ` Michael Ellis
2011-02-21 19:27                           ` Michael Ellis
2011-02-21 20:10                             ` Hans Aberg
2011-02-22 17:32                               ` Michael Ellis

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=AANLkTimJtLOtE75FExKfyWWaNNj3iwWkxd-8WtZLM-Jt@mail.gmail.com \
    --to=michael.f.ellis@gmail.com \
    --cc=bug-guile@gnu.org \
    --cc=wingo@pobox.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).