|
ok.. a minimal test script: In a fresh m4-1.4.1 download: tar -zxvf m4-1.4.1.tar.gz; cd m4-1.4.1.tar.gz the following command gives a bus error after reading line 86 of configure.in: /usr/bin/m4 \ --nesting-limit=9 \ --debug=aflq \ --trace=AC_SUBST_TRACE \ --reload-state=/usr/local/share/autoconf/autoconf/autoconf.m4f \ configure.in ------ > Date: Wed, 18 Aug 2010 14:00:40 +0200 > Subject: Re: [MiNT] automake & configure (m4-1.4.1) > From: miro.kropacek@gmail.com > To: mw333@hotmail.com > CC: mint@lists.fishpool.fi > > > Back to my original problem.. The m4-1.4.1 that I built likes to crash 'Bus > > Error' when used by my system's autom4te, HOWEVER the original system > > m4-1.4.1 doesn't have this problem. > There could be number of reasons -- mintlib has changed, new gcc > produces different (more stack hungry for example) code, ... or even > it might be a hidden bug in mintlib which popped out accidentally. > > > An example command that crashes it is: > > autoconf --verbose (which runs autom4te which runs m4) > And when you run m4 standalone? If standalone works, try to catch m4 > arguments used in autoconf (in 'ps' output for example). > > > - What's an easy way to isolate mintlib daily from the existing system > > libraries? gcc by default wants to look in /usr/local/include and > > /usr/include & /usr/local/lib > make install prefix=/usr/local in mintlib root. but you need to build > it by yourself of course. Or, you can copy stuff from tar.bz2 archive > not into /usr but into /usr/local (file tree is the same). But be sure > gcc really uses it. > > > - Apart from gcc and ld, are there other binaries that I should check ? Is > > there a better ld? > It's most probably some stack / overflow problem. gcc, ld etc should be fine. > > > - What are your favourite gcc options? I'm using CFLAGS="-m68020-60 -Wall" > As do I :) When not sure what's linked in, I use Vincent's -Wl,-t option, too. > > -- > MiKRO / Mystic Bytes > http://mikro.atari.org > > |