From: Anthony Green <green@moxielogic.com>
To: Peter Kruse <pjodrr@gmail.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: libffi 3.0.11 release candidate 2 available for testing
Date: Fri, 18 Nov 2011 15:42:00 -0000 [thread overview]
Message-ID: <4EC67CB1.2020208@moxielogic.com> (raw)
In-Reply-To: <CAAYVSYJbcNqiTdciDAB4-NUx64ONuHxnbpJccp3mDjEXhTTpAA@mail.gmail.com>
On 11/18/2011 2:54 AM, Peter Kruse wrote:
> Hello,
>
> under Solaris 10/Sparc with gcc 4.6.1 and binutils 2.21.1 (ld is
> /usr/ccs/bin/ls) I get on configure:
>
> 2011-11-18 08:29:34 ./configure: line 2649: AX_ENABLE_BUILDDIR:
> command not found
> 2011-11-18 08:29:46 ./configure: line 11842: AX_CC_MAXOPT: command not found
> 2011-11-18 08:29:46 ./configure: line 11843: AX_CFLAGS_WARN_ALL:
> command not found
> 2011-11-18 08:29:49 ./configure: line 13042: GCC_AS_CFI_PSEUDO_OP:
> command not found
Hi Peter,
Did you rebuild the configury or something like that? You would get
this if you ran "aclocal" without the "-I m4" option.
Try running "aclocal -I m4" and then autoconf again.
Thanks,
AG
>
> so there is one more "command not found" since rc1.
> but it does not fail. "make check" results in:
>
> 2011-11-18 08:51:45 === libffi Summary ===
> 2011-11-18 08:51:45
> 2011-11-18 08:51:45 # of expected passes 1634
> 2011-11-18 08:51:45 # of unsupported tests 15
>
> (timestamps are added by my build tool)
>
> Regards,
>
> Peter
next prev parent reply other threads:[~2011-11-18 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 7:54 Peter Kruse
2011-11-18 15:42 ` Anthony Green [this message]
2011-11-23 8:39 ` Peter Kruse
-- strict thread matches above, loose matches on Subject: below --
2011-11-13 4:55 Anthony Green
2011-11-13 12:45 ` Timothy Wall
2011-11-13 13:29 ` Mark Wielaard
2011-11-18 12:09 ` David Gilbert
2011-11-18 16:13 ` Anthony Green
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EC67CB1.2020208@moxielogic.com \
--to=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
--cc=pjodrr@gmail.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).