Can someone check to see if my changes were committed to cvs?  (CHANGES & md5sum.lst)

I think they were committed, but a bunch of errors happened after, which I think were related to emailing the changes out to the list.  So I think the changes were committed but the email failed.

No problem uploading minicom-2.5 to the ftp site anyway.  :-)

Let me know if the CVS changes are committed.  Thanks!

 - BS

On Sat, Feb 12, 2011 at 16:50, Bruce Smith <> wrote:
The weird thing is the "build" portion has the libraries defined, but it aborted in the "install" part, which does not.  I'm not sure why it decided to recompile some of the stuff in the install phase (without the libraries, and abort).

In any case, I tried the latest version of Minicom (2.5) as Heiko suggested.  That builds and installs fine without modifying the build/install script.  I'll upload my fixes later today.

 - BS

On Sat, Feb 12, 2011 at 02:04, Serge Leschinsky <> wrote:

please try this:

 make "LIBS=-lncurses -liconv" $PMAKE all || exit 1


On 02/11/2011 07:51 PM, Bruce Smith wrote:
Hey, sourceforge seems to have cvs fixed now.  I updated and started a fresh
compile.  Unfortunately it aborted installing minicom:

Any clues?

 - BS

Making install in src
make[1]: Entering directory `/data/build/tmp/minicom-2.4/src'
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i686 -march=i686 -Wall -W
 -mtune=i686 -march=i686 -MT minicom.o -MD -MP -MF .deps/minicom.Tpo -c -o
minicom.o minicom.c
mv -f .deps/minicom.Tpo .deps/minicom.Po
gcc -mtune=i686 -march=i686 -Wall -W -mtune=i686 -march=i686   -o minicom
minicom.o vt100.o config.o help.o updown.o util.o d
ial.o window.o wkeys.o ipc.o windiv.o sysdep1.o sysdep1_s.o sysdep2.o rwconf.o
main.o file.o getsdir.o wildmat.o common.o ../
lib/libport.a -lncurses
minicom.o: In function `do_iconv':
minicom.c:(.text+0x69f): undefined reference to `libiconv'
minicom.c:(.text+0x6fc): undefined reference to `libiconv'
minicom.o: In function `.L182':
minicom.c:(.text+0x1947): undefined reference to `libiconv_open'
minicom.o: In function `.L327':
minicom.c:(.text+0x3971): undefined reference to `libiconv_close'
collect2: ld returned 1 exit status
make[1]: *** [minicom] Error 1
make[1]: Leaving directory `/data/build/tmp/minicom-2.4/src'
make: *** [install-recursive] Error 1

The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.

Devil-linux-develop mailing list