On Fri, Feb 08, 2013 at 04:46:28PM -0800, Will Yardley wrote:
On Fri, Feb 08, 2013 at 05:30:03PM -0700, s. keeling wrote:
Incoming from Michael Elkins:
FYI, there are nightly snapshots here http://dev.mutt.org/nightlies/
which avoid the need to have the developer toolchain installed.
I'm trying to build mutt with gcc 3.2.3 on an old Solaris 8 box.
I'm building with:
--with-libiconv-prefix=/software/stow/libiconv-1.14
(I tried with libiconv 1.9.1 first, but got the same error, so tried upgrading)
./configure gives me:
checking whether iconv.h defines iconv_t... yes
checking
Also, if it matters, mutt 1.5.11 definitely built successfully (with
iconv), though since I didn't install it and don't have the
config.status from the old install, I don't know exactly how it was
built.
w
On another system, I can get past the iconv errors in configure.
But both with ncurses 5.2 and the builtin Solaris ncurses, I'm getting:
gcc -Wall -pedantic -Wno-long-long -g -O2 -L/software/stow/openssl-0.9.7d/lib
-L/software/stow/libiconv-1.9.1/lib -o mutt addrbook.o alias.o attach.o
Found some stuff in:
http://compgroups.net/comp.unix.solaris/mutt-1.5-compile-help-solaris-9/439938
and got a little further
Now bailing on:
Undefined first referenced
symbol in file
key_defined keymap.o
Which I think has
I was able to get it to build, after upgrading ncurses. Install failed
until I upgraded autoconf (which in turn required a newer m4).
w
On Fri, Feb 08, 2013 at 02:39:46PM -0800, Will Yardley wrote:
I was able to get it to build, after upgrading ncurses. Install failed
until I upgraded autoconf (which in turn required a newer m4).
Glad you figured that out.
FYI, there are nightly snapshots here
http://dev.mutt.org/nightlies/
On Fri, Feb 08, 2013 at 11:46:45PM +, Michael Elkins wrote:
On Fri, Feb 08, 2013 at 02:39:46PM -0800, Will Yardley wrote:
I was able to get it to build, after upgrading ncurses. Install failed
until I upgraded autoconf (which in turn required a newer m4).
Glad you figured that out.
On Fri, Feb 08, 2013 at 03:48:33PM -0800, Will Yardley wrote:
I noticed some discussion about that. Somehow, though, I had assumed
that the nighlies would still need those tools compared to the current
official dev snapshot. In any event, seems to be working now.
They are built using the same
Incoming from Michael Elkins:
FYI, there are nightly snapshots here http://dev.mutt.org/nightlies/
which avoid the need to have the developer toolchain installed.
Michael, kind of off topic, I know, but why would you want to
discourage people from learning the developer toolchain? Rolling
On Fri, Feb 08, 2013 at 05:30:03PM -0700, s. keeling wrote:
Incoming from Michael Elkins:
FYI, there are nightly snapshots here http://dev.mutt.org/nightlies/
which avoid the need to have the developer toolchain installed.
Michael, kind of off topic, I know, but why would you want to
On Fri, Feb 08, 2013 at 04:46:28PM -0800, Will Yardley wrote:
I think the point is that minimizing the build dependencies for people
who aren't developers should reduce build problems quite a bit.
In this case it was a practical matter where the user wanted to
build Mutt itself, but had auto*
12 matches
Mail list logo
