Daniel Walker | 11 Nov 2008 19:06

Error building autoconf

to whom this concerns,

I am reporting this bug as directed in the failed make attempt  <at>   
autoconf on a Mac OS X workstation.  If available, please advise on a  
work around or a fix while this bug is being addressed.

thanks,

Dan
--->  Building autoconf with target all
Error: Target org.macports.build returned: shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_autoconf/work/autoconf-2.63"
&& make all " returned error 2
Command output: make  all-recursive
Making all in bin
make[2]: Nothing to be done for `all'.
Making all in .
make[2]: Nothing to be done for `all-am'.
Making all in lib
Making all in Autom4te
make[3]: Nothing to be done for `all'.
Making all in m4sugar
make[3]: Nothing to be done for `all'.
Making all in autoconf
autom4te_perllibdir='../..'/lib AUTOM4TE_CFG='../../lib/autom4te.cfg'         ../../bin/autom4te -B
'../..'/lib -B '../..'/lib                              \
        --language=autoconf                     \
        --freeze                        \
(Continue reading)

Eric Blake | 12 Nov 2008 03:41
Gravatar

Re: Error building autoconf


According to Daniel Walker on 11/11/2008 11:06 AM:
> to whom this concerns,
> 
> I am reporting this bug as directed in the failed make attempt  <at> 
> autoconf on a Mac OS X workstation.  If available, please advise on a
> work around or a fix while this bug is being addressed.

Thanks for the report; a SIGBUS should never happen.  I'm guessing from
the error message that this was m4 1.4.12?  (Earlier versions did not trap
SIGBUS).  I don't have access to a Mac OS machine; is there any way you
could help by building m4 with debugging symbols, and capture a stack
trace?  Have you followed the advice to set the MallocHelp environment
variable, and if so, what does that give you?

--
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 <at> byu.net

Gmane