procmail
[Top] [All Lists]

problem compiling procmail 3.22 and 3.15.2 on Solaris 7

2001-11-30 07:46:16
I am trying to install procmail on a Solaris 7 box (Fujitsu M800). I have
tried both 3.22 and 3.15.2, both fail. I am using gcc 3.0.1 for compiling
the source code. Following is the output of the session. As you will note
the install starts fine, even completes the kernel lock tests, but pukes
after that. I couldn't find any references to the errors.
Any help is greatly appreciated.

Zahid
*************************************************************

# make install
/bin/sh ./initmake /bin/sh "/bin/sh" "/bin/rm -f" "mv -f" "ln" \
 "-lm -ldir -lx -lsocket -lnet -linet -lnsl_s -lnsl_i -lnsl -lsun  -lgen
-lsockd
ns -ldl" \
 "/lib /usr/lib /usr/local/lib" \
 /dev/null "make" o \
 "gcc" "-O" "-s " "procmail lockfile formail mailstat" \
 "procmail formail lockfile" \
 "procmailrc procmailsc procmailex" "src man" \
 "/usr/local/bin" \
 "strip"
gcc seems to work fine, using that as the C-compiler
        ...scanning for 13 libraries...
Added LDFLAGS= -lm -lsocket -lnsl -lgen -ldl -lc
make make install
cd src; make ../autoconf.h
/bin/sh ./autoconf /bin/sh "/bin/rm -f" "mv -f" /dev/null \
 "fgrep" "make" o "__defaults__" \
 "/usr/local/bin" ../autoconf.h
============================================================================
==
In order for the kernel-locking tests to work as intended I have to be able
to
test-lock files on as many semantically different filesystems as possible
(for
more information about this, READ PARAGRAPH TWO in INSTALL).  To suppress
this
prompt you can set the LOCKINGTEST variable in the Makefile.

Please add writable directories to the list.  You should only add
directories
that reside on filesystems that have unique characteristics.  E.g. if you
have
several remote NFS partitions, pick some unique client-server pairs, there
is
little use in picking the same server twice from the same client-machine.
An excellent candidate would be a remotely mounted mail spool directory.
============================================================================
==


I will temporarily use a testdirectory named _locktest
in the following directories:

/tmp .

If you would like to add any, please specify them below,
press return to continue:


Initiating fcntl()/kernel-locking-support tests

Proceeding with kernel-locking-support tests in the background
Testing for const
Testing for volatile
Testing for prototypes
Testing for enum
Checking for POSIX and ANSI/ISO system include files
Checking for network/comsat/biff support
Testing for void*, size_t, off_t, pid_t, time_t, mode_t, uid_t & gid_t
Checking realloc implementation
Testing for WIFEXITED(), WIFSTOPPED(), WEXITSTATUS() & WSIGTERM()
Testing for various struct passwd members
Testing for memmove, strchr, strpbrk, strcspn, strtol, strstr,
        rename, setrgid, setegid, pow, opendir, mkdir, waitpid, fsync,
        ftruncate, strtod, strncasecmp, strerror, strlcat,
        memset, bzero, and _exit
Determining the maximum number of 16 byte arguments execv() takes
Benchmarking your system's strstr() implementation
Waiting for the kernel-locking tests to finish...
Every two digits a file is locked.  First digit: which file, second digit:
which program, XX indicates a lock conflict or failure

Starting test 4 on /tmp/_locktest
 17 05 16 11 04 10 03 15 02 11 07 14 06 05 10 01 13 04 12 00 17 16 01 15 03
14 0
2 15 13 00 14 07 12 06 17 16 01 05 11 03 15 00 13 04 10 02 14 12 07 06 01 11
05 
11 03 15 13 00 04 10 10 02 14 07 12 06
Starting test 4 on ./_locktest
 07 14 06 13 05 12 02 02 11 02 01 10 01 01 17 00 00 14 16 04 13 03 15 12 11
10 1
7 14 07 07 16 13 06 15 12 05 11 02 10 01 14 17 04 04 16 07 13 04 15 06 07 12
03 
10 05 11 14 02 16 17 03 10 01 06 15
Starting test 6 on /tmp/_locktest
 17 06 12 05 04 03 11 02 04 10 03 17 01 16 15 04 12 00 11 03 14 07 10 13 06
16 0
5 02 10 15 01 04 14 07 17 03 13 06 02 12 00 10 05 10 01 11 04 07 03 06 16 02
05 
15 00 10 01 04 14 07 17 03 17 06 13
Starting test 6 on ./_locktest
 14 07 06 05 04 04 13 03 03 12 02 11 01 10 00 17 07 16 06 15 06 05 14 05 13
12 0
2 11 01 10 00 17 16 00 00 14 15 13 12 02 11 17 07 16 10 01 00 14 00 15 04 13
03 
12 02 17 16 11 15 01 14 04 13 03 12
Starting test 7 on /tmp/_locktest
XX10 02XX22XX8XX1a


Collecting results from kernel-locking tests
=============================autoconf.h===================================
/* This file was automagically generated by autoconf */

#define NOpw_class
#define NOstrlcat
#define NOsetrgid
#define GOT_bin_test
#define MAX_argc 49800
/* Your system's strstr() is 1.00 times SLOWER than my C-routine */
#define UDP_protocolno 17
#define BIFF_serviceport "512"
#define IP_localhost {127,0,0,1}
#define TOGGLE_SGID_OK
#define MAILSPOOLDIR "/var/mail/"
#define SENDMAIL "/usr/lib/sendmail"
#define CF_no_procmail_yet
#define defPATH "PATH=$HOME/bin:/bin:/usr/ucb:/usr/local/bin:/usr/X/bin"
#define defSPATH "PATH=/bin:/usr/ucb:/usr/local/bin:/usr/X/bin"
#define PM_VERSION "3.22"
/*locktype: 4, countlocks: 0, timeout 0, watchdog 8, /tmp/_locktest*/
/*locktype: 4, countlocks: 0, timeout 0, watchdog 8, ./_locktest*/
/*locktype: 6, countlocks: 0, timeout 0, watchdog 8, /tmp/_locktest*/
/*locktype: 6, countlocks: 0, timeout 0, watchdog 8, ./_locktest*/
/*locktype: 7, countlocks: 80, timeout 0, watchdog 14, /tmp/_locktest*/
/* Hotwire LOCKINGTEST=110 */
/* Procmail will lock via: dotlocking, fcntl(), lockf() */
#define USElockf
/* autoconf completed */
==========================================================================
echo Housekeeping file >config.check
cd man; make ../new/procmail.1 ../new/formail.1 ../new/lockfile.1
../new/procmai
lrc.5 ../new/procmailsc.5 ../new/procmailex.5
/bin/sh ./mansed /bin/sh procmail.man procmail.1 "/bin/rm -f" /dev/null
ln ../man/procmail.1 ../new/procmail.1
/bin/sh ./mansed /bin/sh formail.man formail.1 "/bin/rm -f" /dev/null
ln ../man/formail.1 ../new/formail.1
/bin/sh ./mansed /bin/sh lockfile.man lockfile.1 "/bin/rm -f" /dev/null
ln ../man/lockfile.1 ../new/lockfile.1
/bin/sh ./mansed /bin/sh procmailrc.man procmailrc.5 "/bin/rm -f" /dev/null
ln ../man/procmailrc.5 ../new/procmailrc.5
/bin/sh ./mansed /bin/sh procmailsc.man procmailsc.5 "/bin/rm -f" /dev/null
ln ../man/procmailsc.5 ../new/procmailsc.5
/bin/sh ./mansed /bin/sh procmailex.man procmailex.5 "/bin/rm -f" /dev/null
ln ../man/procmailex.5 ../new/procmailex.5
echo Housekeeping file >install.man
cd src; make ../new/procmail ../new/lockfile ../new/formail ../new/mailstat
gcc -c -O procmail.c
/usr/ccs/bin/as: "/var/tmp/ccFZXAYI.s", line 1487: error: unknown opcode
".subse
ction"
/usr/ccs/bin/as: "/var/tmp/ccFZXAYI.s", line 1487: error: statement syntax
/usr/ccs/bin/as: "/var/tmp/ccFZXAYI.s", line 1613: error: unknown opcode
".previ
ous"
/usr/ccs/bin/as: "/var/tmp/ccFZXAYI.s", line 1613: error: statement syntax
*** Error code 1
make: Fatal error: Command failed for target `procmail.o'
Current working directory /usr/local/packages/procmail/procmail-3.22/src
*** Error code 1
make: Fatal error: Command failed for target `bins'
Current working directory /usr/local/packages/procmail/procmail-3.22
*** Error code 1
make: Fatal error: Command failed for target `install'
Current working directory /usr/local/packages/procmail/procmail-3.22
*** Error code 1
make: Fatal error: Command failed for target `install'


_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>
  • problem compiling procmail 3.22 and 3.15.2 on Solaris 7, Naqvi Zahid - znaqvi <=