[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] automake & configure (m4-1.4.1)



Thanks for all your help.

I found I could build m4-1.4.1, m4-1.4.2, m4-1.4.3 and m4-1.4.4 and get all tests to pass successfully,
I also decided to build less (which requires ncurses and terminfo) and the building seems to work, but the resulting binary is not useful, perhaps because the ncurses-dev and terminfo are a bit out of date (2000).  I recall someone on the list had built these recently, I might give it another go if you want to mail a link to these rpms/libs..

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.
An example command that crashes it is:
autoconf --verbose (which runs autom4te which runs m4)

My theories as to whats going on are:
1. mint has another set of flags that lets software grow by > 1 meg [but perl is already using 5 meg and I've set mint.cnf TPA_INITIALMEM=4096, i've also tried setting stack to 1meg, and flags reports 0x07 which is the same as other binaries eg: perl ]
2. an old library I have is interacting / interfering with the new libraries
3. there's a secret gcc option that mint people use [my references at the moment are http://sparemint.org/sparemint/mint/mintlib/IMPORTANT and 
http://vincent.riviere.free.fr/soft/m68k-atari-mint/]
4. my ld (or other tool I don't know about) is broken

Here are some version numbers:

GNU ld (GNU Binutils for MiNT 20100410) 2.20.1.20100303
Copyright 2009 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.

gcc (GCC) 4.5.0 (MiNT 20100511)
Copyright (C) 2010 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.

my gcc2 is:
2.95.3
(165839 bytes, datestamp = Jun 17)

So, some specific easy questions:
- 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
- Apart from gcc and ld, are there other binaries that I should check ? Is there a better ld?
- What are your favourite gcc options? I'm using CFLAGS="-m68020-60 -Wall"

Thanks for pointers.

Matt.

> Date: Fri, 13 Aug 2010 21:18:43 +0200
> Subject: Re: [MiNT] automake & configure (m4-1.4.1)
> From: miro.kropacek@gmail.com
> To: mw333@hotmail.com
> CC: mint@lists.fishpool.fi
>
> > I thought I'd try and get m4-1.4.1 to compile from source [because there's
> > already one in sparemint, and I'd guess m4 is a fairly basic gnu utility]
> m4 isn't exactly the best idea. I might be wrong but I think it wasn't
> totally easy to compile, t required some more steps. Better take
> something like simpler ('less' comes to my mind).
>
> > configure:2796: checking for library containing strerror
> > configure:2826: gcc -o conftest -g -O2   conftest.c  >&5
> > /usr/bin/ld: cannot find -lc_g
> Our old and well known problem which should have been removed ...
> (when, Vincent?) You must disable usage of '-g' switch or (uglier but
> faster) make a symlink libc_g.a -> libc.a in /usr/lib.
>
> --
> MiKRO / Mystic Bytes
> http://mikro.atari.org