Hi,
This is my first time with procmail/SmartList and 'am having trouble building procmail 3.22.
Find below the contents of output to the console:
root@test:/maint/procmail-3.22-# make install-suid /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 "/lib /usr/lib /usr/local/lib /usr/share/lib" \ /dev/null "make" o \ "cc" "-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-suid 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 -- output edited as no error messages were displayed -- /* autoconf completed */ ======================================================================= gcc -c -O sublib.c ======================================================================= If you are a system administrator you should consider integrating procmail into the mail-delivery system -- for advanced functionality, speed AND SECURITY --. For more information about this topic you should look in the examples/advanced file. Also, HIGHLY RECOMMENDED (type 'make install-suid' to execute it): chown root /usr/local/SmartList/bin/procmail chgrp mail /usr/local/SmartList/bin/procmail /usr/local/SmartList/bin/lockfile chmod 6755 /usr/local/SmartList/bin/procmail chmod 2755 /usr/local/SmartList/bin/lockfile ======================================================================= cd src; make ../new/procmail ../new/lockfile ../new/formail ../new/mailstat gcc -c -O procmail.c /usr/ccs/bin/as: "/var/tmp/ccvGjLaB.s", line 1487: error: unknown opcode ".subsection" /usr/ccs/bin/as: "/var/tmp/ccvGjLaB.s", line 1487: error: statement syntax /usr/ccs/bin/as: "/var/tmp/ccvGjLaB.s", line 1613: error: unknown opcode ".previous" /usr/ccs/bin/as: "/var/tmp/ccvGjLaB.s", line 1613: error: statement syntax *** Error code 1 make: Fatal error: Command failed for target `procmail.o' Current working directory /usr/local/procmail-3.22/src *** Error code 1 make: Fatal error: Command failed for target `bins'
And the output of uname -a:
SunOS test 5.8 Generic_108528-12 sun4u sparc SUNW,UltraAX-i2
Would appreciate any help with the build.
Regards,
Sanil
Hello,
"SGopal" == "Gopal, Sanil (CTR)" <SGopal@hq.odedodea.edu> writes:
SGopal> Hi, SGopal> SGopal> This is my first time with procmail/SmartList and 'am SGopal> having trouble building procmail 3.22. SGopal> SGopal> Find below the contents of output to the console: SGopal> [...] SGopal> /usr/ccs/bin/as: "/var/tmp/ccvGjLaB.s", line 1487: SGopal> error: unknown opcode ".subsection" Sounds to me like gcc gets the wrong "assembler" (= "compiler" for assembler code). This may be because your $PATH lists /usr/ccs/bin before the directory where gcc (and hopefully the GNU assembler) is. It may also be because the GNU assembler is called "gas" in your installation. Try to add the directory where gcc lives in front of your PATH. If this does not help, there is probably some way to tell gcc which assembler to use. Sorry, I don't know how to achieve this (didn't find it in the man page), and I don't know how to tell the procmail configure process to pass this information to gcc (I currently have no procmail sources at hand). Hans-Albert -- Hans-Albert Schneider Munich, Germany EMail: Hans-Albert@HA-Schneider.de
participants (2)
-
Gopal, Sanil (CTR)
-
Hans-Albert Schneider