Re: does this compile error look fmailiar?
On Wed, Dec 30, 2009 at 01:30:16PM -0600, Dustin J. Mitchell wrote:
On Wed, Dec 30, 2009 at 1:03 PM, stan st...@panix.com wrote:
urity.c ??-fPIC -DPIC -o .libs/bsd-security.o
In file included from bsd-security.c:33:
util.h:349: error: parse error before in_port_t
util.h:350: warning: function declaration isn't a prototype
I suspect this patch might help:
http://github.com/zmanda/amanda/commit/911a9b5fbf136ee0dbffcae4e9696be498491c43
Debbie reminded me that we really need 2.5.2, so I tried building 2.5.2p1,
whch failed ad follows:
Script started on Thu Dec 31 12:02:01 2009
AP0502# make
Making all in gnulib
{ echo '/* DO NOT EDIT! GENERATED AUTOMATICALLY! */'; \
cat ./alloca_.h; \
} alloca.h-t
mv -f alloca.h-t alloca.h
rm -f string.h-t string.h
{ echo '/* DO NOT EDIT! GENERATED AUTOMATICALLY! */' \
sed -e 's|@''ABSOLUTE_STRING_H''@|///usr/include/string.h|g' \
-e 's|@''HAVE_DECL_MEMMEM''@|1|g' \
-e 's|@''HAVE_MEMPCPY''@|1|g' \
-e 's|@''HAVE_DECL_MEMRCHR''@|1|g' \
-e 's|@''HAVE_STPCPY''@|1|g' \
-e 's|@''HAVE_STPNCPY''@|1|g' \
-e 's|@''HAVE_DECL_STRNCASECMP''@|1|g' \
-e 's|@''HAVE_STRCHRNUL''@|1|g' \
-e 's|@''HAVE_DECL_STRDUP''@|1|g' \
-e 's|@''HAVE_STRNDUP''@|1|g' \
-e 's|@''HAVE_DECL_STRNDUP''@|1|g' \
-e 's|@''HAVE_DECL_STRNLEN''@|1|g' \
-e 's|@''HAVE_STRPBRK''@|1|g' \
-e 's|@''HAVE_STRSEP''@|1|g' \
-e 's|@''HAVE_DECL_STRTOK_R''@|1|g' \
-e 's|@''REPLACE_STRCASECMP''@|0|g' \
-e 's|@''REPLACE_STRSTR''@|0|g' \
-e 's|@''REPLACE_STRCASESTR''@|0|g' \
./string_.h; \
} string.h-t
mv string.h-t string.h
make all-am
if /bin/ksh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I../config -D_REENTRANT -Wall -Wextra -Wparentheses
-Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes
-Wmissing-declarations -Wformat -Wsign-compare -Wfloat-equal
-Wold-style-definition -Wno-error -D_GNU_SOURCE -MT lock.lo -MD -MP -MF
.deps/lock.Tpo -c -o lock.lo lock.c; \
then mv -f .deps/lock.Tpo .deps/lock.Plo; else rm -f .deps/lock.Tpo; exit
1; fi
mkdir .libs
gcc -DHAVE_CONFIG_H -I. -I. -I../config -D_REENTRANT -Wall -Wextra
-Wparentheses -Wdeclaration-after-statement -Wmissing-prototypes
-Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare
-Wfloat-equal -Wold-style-definition -Wno-error -D_GNU_SOURCE -MT lock.lo -MD
-MP -MF .deps/lock.Tpo -c lock.c -fPIC -DPIC -o .libs/lock.o
lock.c:361: warning: missing braces around initializer
lock.c:361: warning: (near initialization for `fresh_once.pthread_once_pad')
gcc -DHAVE_CONFIG_H -I. -I. -I../config -D_REENTRANT -Wall -Wextra
-Wparentheses -Wdeclaration-after-statement -Wmissing-prototypes
-Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare
-Wfloat-equal -Wold-style-definition -Wno-error -D_GNU_SOURCE -MT lock.lo -MD
-MP -MF .deps/lock.Tpo -c lock.c -o lock.o /dev/null 21
if /bin/ksh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I../config -D_REENTRANT -Wall -Wextra -Wparentheses
-Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes
-Wmissing-declarations -Wformat -Wsign-compare -Wfloat-equal
-Wold-style-definition -Wno-error -D_GNU_SOURCE -MT asnprintf.lo -MD -MP -MF
.deps/asnprintf.Tpo -c -o asnprintf.lo asnprintf.c; \
then mv -f .deps/asnprintf.Tpo .deps/asnprintf.Plo; else rm -f
.deps/asnprintf.Tpo; exit 1; fi
gcc -DHAVE_CONFIG_H -I. -I. -I../config -D_REENTRANT -Wall -Wextra
-Wparentheses -Wdeclaration-after-statement -Wmissing-prototypes
-Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare
-Wfloat-equal -Wold-style-definition -Wno-error -D_GNU_SOURCE -MT asnprintf.lo
-MD -MP -MF .deps/asnprintf.Tpo -c asnprintf.c -fPIC -DPIC -o .libs/asnprintf.o
gcc -DHAVE_CONFIG_H -I. -I. -I../config -D_REENTRANT -Wall -Wextra
-Wparentheses -Wdeclaration-after-statement -Wmissing-prototypes
-Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare
-Wfloat-equal -Wold-style-definition -Wno-error -D_GNU_SOURCE -MT asnprintf.lo
-MD -MP -MF .deps/asnprintf.Tpo -c asnprintf.c -o asnprintf.o /dev/null 21
if /bin/ksh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I../config -D_REENTRANT -Wall -Wextra -Wparentheses
-Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes
-Wmissing-declarations -Wformat -Wsign-compare -Wfloat-equal
-Wold-style-definition -Wno-error -D_GNU_SOURCE -MT gai_strerror.lo -MD -MP -MF
.deps/gai_strerror.Tpo -c -o gai_strerror.lo gai_strerror.c; \
then mv -f .deps/gai_strerror.Tpo .deps/gai_strerror.Plo; else rm -f
.deps/gai_strerror.Tpo; exit 1; fi
gcc -DHAVE_CONFIG_H -I. -I. -I../config -D_REENTRANT -Wall -Wextra
-Wparentheses -Wdeclaration-after-statement -Wmissing-prototypes
-Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare
-Wfloat-equal -Wold-style-definition -Wno-error -D_GNU_SOURCE -MT
gai_strerror.lo -MD -MP -MF
Re: does this compile error look fmailiar?
On Thu, Dec 31, 2009 at 11:12 AM, stan st...@panix.com wrote: This looks similar, but I am having a hard time believeg that the atch you mentioned yesterday did not get applied to the 2.5.2 tree. Is that correct? Do I need to apply that patch to 2.5.2p1? Yep. Dustin -- Open Source Storage Engineer http://www.zmanda.com
does this compile error look fmailiar?
I am trying to build 2.5.1p2 on a Solaris 5 machine that i just confirmed I can build 2.4.3b4 on this morning, so I know I have a somewhat sane build environment. configure seems happy, but the compile fails fairly quickly with this error. Any thoughts? urity.c -fPIC -DPIC -o .libs/bsd-security.o In file included from bsd-security.c:33: util.h:349: error: parse error before in_port_t util.h:350: warning: function declaration isn't a prototype -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: does this compile error look fmailiar?
On Wed, Dec 30, 2009 at 1:03 PM, stan st...@panix.com wrote: urity.c -fPIC -DPIC -o .libs/bsd-security.o In file included from bsd-security.c:33: util.h:349: error: parse error before in_port_t util.h:350: warning: function declaration isn't a prototype I suspect this patch might help: http://github.com/zmanda/amanda/commit/911a9b5fbf136ee0dbffcae4e9696be498491c43 Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: does this compile error look fmailiar?
On Wed, Dec 30, 2009 at 01:30:16PM -0600, Dustin J. Mitchell wrote: On Wed, Dec 30, 2009 at 1:03 PM, stan st...@panix.com wrote: urity.c ??-fPIC -DPIC -o .libs/bsd-security.o In file included from bsd-security.c:33: util.h:349: error: parse error before in_port_t util.h:350: warning: function declaration isn't a prototype I suspect this patch might help: http://github.com/zmanda/amanda/commit/911a9b5fbf136ee0dbffcae4e9696be498491c43 Cool, thanks. Out of time today, and won't be back to work till (at least) Mondy, perhaps Tuesday, but i will try to find time to work on it then. Deb says we need 2.5.2, anyway, but I do have a working Soalri 5 build environement again, albeit ona production amchine. I might try to clone that machien to the one in the lab. -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
amanda-2.6.2p1 compile error on Solaris 10
SYSTEM: SunOS zorn.math.purdue.edu 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-280R AMANDA: 2.6.1p1 When I run configure I get the following error. | ; | return 0; | } configure:53701: error: in `/pkgs/src/amanda-server/amanda-2.6.1p1': configure:53704: error: cannot compute sizeof (size_t) See `config.log' for more details. Any ideas what might be causing this? Is this a know problem that needs a patch? Here is my local.configure local.configure 28 lines, 651 characters #! /bin/sh ## # AMANDAVERSION=amanda-2.6.1p1 # ## GCCVERSION=gcc-3.4.3 #CC=/pkgs/$GCCVERSION/bin/gcc #export CC ./configure \ CC=/pkgs/$GCCVERSION/bin/gcc \ MT=/opt/csw/bin/mt \ MTF=-f \ MTX=/opt/csw/sbin/mtx \ PERL=/opt/csw/bin/perl \ --prefix=/local/Amanda/$AMANDAVERSION \ --with-user=amanda \ --with-group=operator \ --with-gnutar=/opt/csw/bin/gtar \ --with-gnutar-listdir=/var/amanda/gnutar-lists \ --with-includes=/opt/csw/include \ --with-libraries=/opt/csw/lib \ --with-index-server=zorn \ --with-smbclient=/pkgs/samba/bin/smbclient \ --with-tape-device=/dev/rmt/1bn \ --with-changer-device=/dev/changer/1 _ Robert P. McGraw, Jr. Manager, Computer SystemEMAIL: rmcg...@purdue.edu Purdue UniversityROOM: MATH-807 Department of Mathematics PHONE: (765) 494-6055 150 N. University Street West Lafayette, IN 47907-2067
Re: amanda-2.6.2p1 compile error on Solaris 10
I just released 2.6.1.p1 + patches for the FSF_AFTER_FILEMARK Solaris bug, and amsuntar rev-1905 to the OpenCSW 'current' repository last week. I see that you're using some OpenCSW/Blastwave packages so the package might save you some time. McGraw, Robert P wrote: SYSTEM: SunOS zorn.math.purdue.edu 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-280R AMANDA: 2.6.1p1 When I run configure I get the following error. | ; | return 0; | } configure:53701: error: in `/pkgs/src/amanda-server/amanda-2.6.1p1': configure:53704: error: cannot compute sizeof (size_t) See `config.log' for more details. Any ideas what might be causing this? Is this a know problem that needs a patch? Here is my local.configure local.configure 28 lines, 651 characters #! /bin/sh ## # AMANDAVERSION=amanda-2.6.1p1 # ## GCCVERSION=gcc-3.4.3 #CC=/pkgs/$GCCVERSION/bin/gcc #export CC ./configure \ CC=/pkgs/$GCCVERSION/bin/gcc \ MT=/opt/csw/bin/mt \ MTF=-f \ MTX=/opt/csw/sbin/mtx \ PERL=/opt/csw/bin/perl \ --prefix=/local/Amanda/$AMANDAVERSION \ --with-user=amanda \ --with-group=operator \ --with-gnutar=/opt/csw/bin/gtar \ --with-gnutar-listdir=/var/amanda/gnutar-lists \ --with-includes=/opt/csw/include \ --with-libraries=/opt/csw/lib \ --with-index-server=zorn \ --with-smbclient=/pkgs/samba/bin/smbclient \ --with-tape-device=/dev/rmt/1bn \ --with-changer-device=/dev/changer/1 -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 Phone: 716-633-3463 Email: darin...@cognigencorp.com
amanda-2.4.4p4 compile error on solaris 8
Hi, I try to compile amanda-2.4.4p4 on solaris 8 to get the amrecover_changer option (we run now amanda-2.4.3): [EMAIL PROTECTED] /root]# uname -a SunOS backup-a01 5.8 Generic_108528-16 sun4u sparc SUNW,Ultra-250 When I try to use the following config command: [EMAIL PROTECTED] amanda-2.4.4p4]# ./configure --with-user=amanda --with-group=sys --with-amandahosts --with-includes=/usr/local/include --with-libraries=/usr/local/lib --with-tape-device=/dev/rmt/1n --with-tape-changer=/dev/scsi/changer/c7t1d0 --prefix=/usr01/app/amanda-2.4.4p4 --with-config=DailyBackup --with-gnutar=/usr/local/bin/tar I get the following error: ... ld: fatal: relocations remain against allocatable but non-writable sections collect2: ld returned 1 exit status make[1]: *** [libamanda.la] Error 1 make[1]: Leaving directory `/export/home/mov04995/amanda-2.4.4p4/common-src' make: *** [all-recursive] Error 1 [EMAIL PROTECTED] amanda-2.4.4p4]# When I try to use the following config command: [EMAIL PROTECTED] amanda-2.4.4p4]$ ./configure --host=sun4 --target=sparc-sun-solaris2.8 --with-user=amanda --with-group=sys --with-amandahosts --with-includes=/usr/local/include --with-libraries=/usr/local/lib --with-tape-device=/dev/rmt/1n --with-tape-changer=/dev/scsi/changer/c7t1d0 --prefix=/usr01/app/amanda-2.4.4p4 --with-config=DailyBackup --with-gnutar=/usr/local/bin/tar --with-gnu-ld I get the following error: gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -MT sl.lo -MD -MP -MF .deps/sl.Tpo -c sl.c -DPIC cc1: warning: changing search order for system directory /usr/local/include cc1: warning: as it has already been specified as a non-system directory mv -f sl.o .libs/sl.o gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -MT sl.lo -MD -MP -MF .deps/sl.Tpo -c sl.c /dev/null 21 /bin/bash ../libtool --mode=link gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2-R/usr/local/lib -L/usr/local/lib -o libamanda.la -rpath /usr01/app/amanda-2.4.4p4/lib -release 2.4.4p4 alloc.lo amflock.lo clock.lo debug.lo dgram.lo error.lo file.lo fileheader.lo amfeatures.lo match.lo protocol.lo regcomp.lo regerror.lo regexec.lo regfree.lo security.lo statfs.lo stream.lo token.lo util.lo versuff.lo version.lo pipespawn.lo sl.lo -lgen -lm -ltermcap -lsocket -lnsl -lintl *** Warning: inter-library dependencies are not known to be supported. *** All declared inter-library dependencies are being dropped. *** The inter-library dependencies that have been dropped here will be *** automatically added whenever a program is linked with this library *** or is declared to -dlopen it. /usr/ccs/bin/ld -assert pure-text -Bstatic -o .libs/libamanda-2.4.4p4.so.0.0 .libs/alloc.o .libs/amflock.o .libs/clock.o .libs/debug.o .libs/dgram.o .libs/error.o .libs/file.o .libs/fileheader.o .libs/amfeatures.o .libs/match.o .libs/protocol.o .libs/regcomp.o .libs/regerror.o .libs/regexec.o .libs/regfree.o .libs/security.o .libs/statfs.o .libs/stream.o .libs/token.o .libs/util.o .libs/versuff.o .libs/version.o .libs/pipespawn.o .libs/sl.o ld: fatal: file pure-text: open failed: No such file or directory make[1]: *** [libamanda.la] Error 1 make[1]: Leaving directory `/export/home/mov04995/amanda-2.4.4p4/common-src' make: *** [all-recursive] Error 1 [EMAIL PROTECTED] amanda-2.4.4p4]$ Some system details: [EMAIL PROTECTED] amanda-2.4.4p4]$ echo $PATH /usr/bin::/usr/local/bin:/usr/ucb:/usr/ccs/bin [EMAIL PROTECTED] amanda-2.4.4p4]$ echo $LD_LIBRARY_PATH [EMAIL PROTECTED] amanda-2.4.4p4]$ [EMAIL PROTECTED] amanda-2.4.4p4]$ type ld ld is /usr/local/bin/ld [EMAIL PROTECTED] amanda-2.4.4p4]$ [EMAIL PROTECTED] amanda-2.4.4p4]$ pkginfo -l SMCgcc PKGINST: SMCgcc NAME: gcc CATEGORY: application ARCH: sparc VERSION: 3.1 BASEDIR: /usr/local VENDOR: Free Software Foundation PSTAMP: Steve Christensen INSTDATE: Oct 29 2002 10:59 EMAIL: [EMAIL PROTECTED] STATUS: completely installed FILES: 1801 installed pathnames 47 shared pathnames 10 linked files 139 directories 43 executables 543124 blocks used (approx) [EMAIL PROTECTED] amanda-2.4.4p4]$ Can you please help me with some ideas about how to compile this version of amanda on solaris 8? Thank you very much, Radu
Re: amanda-2.4.4p4 compile error on solaris 8
On Thu, Feb 10, 2005 at 01:33:53PM +, Rolinux wrote: Hi, I try to compile amanda-2.4.4p4 on solaris 8 to get the amrecover_changer option (we run now amanda-2.4.3): [EMAIL PROTECTED] /root]# uname -a SunOS backup-a01 5.8 Generic_108528-16 sun4u sparc SUNW,Ultra-250 ... Some system details: [EMAIL PROTECTED] amanda-2.4.4p4]$ echo $PATH /usr/bin::/usr/local/bin:/usr/ucb:/usr/ccs/bin [EMAIL PROTECTED] amanda-2.4.4p4]$ echo $LD_LIBRARY_PATH [EMAIL PROTECTED] amanda-2.4.4p4]$ [EMAIL PROTECTED] amanda-2.4.4p4]$ type ld ld is /usr/local/bin/ld Many (most?) gcc installations on Solaris use the standard Sun provided assembler and linker. Is there a specific reason you are not using the Sun linker? Perhaps move /usr/ccs/bin in your path before /usr/local/bin. [EMAIL PROTECTED] amanda-2.4.4p4]$ [EMAIL PROTECTED] amanda-2.4.4p4]$ pkginfo -l SMCgcc PKGINST: SMCgcc NAME: gcc CATEGORY: application ARCH: sparc VERSION: 3.1 BASEDIR: /usr/local VENDOR: Free Software Foundation ... Can you please help me with some ideas about how to compile this version of amanda on solaris 8? Many gcc installations for Solaris include a script called something like fixheaders. Does your gcc package have such a script and has it been run? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amanda-2.4.4p4 compile error on solaris 8
On Thursday 10 February 2005 15:46, Jon LaBadie wrote: On Thu, Feb 10, 2005 at 01:33:53PM +, Rolinux wrote: Hi, I try to compile amanda-2.4.4p4 on solaris 8 to get the amrecover_changer option (we run now amanda-2.4.3): [EMAIL PROTECTED] /root]# uname -a SunOS backup-a01 5.8 Generic_108528-16 sun4u sparc SUNW,Ultra-250 ... Some system details: [EMAIL PROTECTED] amanda-2.4.4p4]$ echo $PATH /usr/bin::/usr/local/bin:/usr/ucb:/usr/ccs/bin [EMAIL PROTECTED] amanda-2.4.4p4]$ echo $LD_LIBRARY_PATH [EMAIL PROTECTED] amanda-2.4.4p4]$ [EMAIL PROTECTED] amanda-2.4.4p4]$ type ld ld is /usr/local/bin/ld Many (most?) gcc installations on Solaris use the standard Sun provided assembler and linker. Is there a specific reason you are not using the Sun linker? Perhaps move /usr/ccs/bin in your path before /usr/local/bin. Same error: execve 0x514 .libs/pipespawn.o execve 0xc0c .libs/pipespawn.o __cmpdi20x3c.libs/statfs.o __cmpdi20xb8.libs/statfs.o __cmpdi20x134 .libs/statfs.o __floatdidf 0x50.libs/statfs.o __floatdidf 0xcc.libs/statfs.o __floatdidf 0x148 .libs/statfs.o __floatdidf 0x1e0 .libs/statfs.o __floatdidf 0x244 .libs/statfs.o __floatdidf 0x2a8 .libs/statfs.o ld: fatal: relocations remain against allocatable but non-writable sections collect2: ld returned 1 exit status *** Error code 1 make: Fatal error: Command failed for target `libamanda.la' Current working directory /export/home/mov04995/amanda-2.4.4p4/common-src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' [EMAIL PROTECTED] amanda-2.4.4p4]$ echo $PATH /usr/bin::/usr/ccs/bin:/usr/local/bin:/usr/ucb:/usr/local/samba/bin [EMAIL PROTECTED] amanda-2.4.4p4]$ [EMAIL PROTECTED] amanda-2.4.4p4]$ [EMAIL PROTECTED] amanda-2.4.4p4]$ pkginfo -l SMCgcc PKGINST: SMCgcc NAME: gcc CATEGORY: application ARCH: sparc VERSION: 3.1 BASEDIR: /usr/local VENDOR: Free Software Foundation ... Can you please help me with some ideas about how to compile this version of amanda on solaris 8? Many gcc installations for Solaris include a script called something like fixheaders. Does your gcc package have such a script and has it been run? [EMAIL PROTECTED] /]# find / -name fixheaders -print [EMAIL PROTECTED] /]# No fixheaders Thank you, Radu
Re: amanda-2.4.4p4 compile error on solaris 8
On Thu, Feb 10, 2005 at 04:21:35PM +, Rolinux wrote: On Thursday 10 February 2005 15:46, Jon LaBadie wrote: On Thu, Feb 10, 2005 at 01:33:53PM +, Rolinux wrote: Hi, I try to compile amanda-2.4.4p4 on solaris 8 to get the amrecover_changer option (we run now amanda-2.4.3): [EMAIL PROTECTED] /root]# uname -a SunOS backup-a01 5.8 Generic_108528-16 sun4u sparc SUNW,Ultra-250 ... Some system details: [EMAIL PROTECTED] amanda-2.4.4p4]$ echo $PATH /usr/bin::/usr/local/bin:/usr/ucb:/usr/ccs/bin [EMAIL PROTECTED] amanda-2.4.4p4]$ echo $LD_LIBRARY_PATH [EMAIL PROTECTED] amanda-2.4.4p4]$ [EMAIL PROTECTED] amanda-2.4.4p4]$ type ld ld is /usr/local/bin/ld Many (most?) gcc installations on Solaris use the standard Sun provided assembler and linker. Is there a specific reason you are not using the Sun linker? Perhaps move /usr/ccs/bin in your path before /usr/local/bin. Same error: ... ld: fatal: relocations remain against allocatable but non-writable sections collect2: ld returned 1 exit status *** Error code 1 make: Fatal error: Command failed for target `libamanda.la' Current working directory /export/home/mov04995/amanda-2.4.4p4/common-src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' [EMAIL PROTECTED] amanda-2.4.4p4]$ echo $PATH /usr/bin::/usr/ccs/bin:/usr/local/bin:/usr/ucb:/usr/local/samba/bin [EMAIL PROTECTED] amanda-2.4.4p4]$ Does amanda know about that. It may have recorded the location of cc, ld, ... when you did your configure. Did you reconfigure after the PATH change? BTW, before rerunning ./configure, get rid of all previous configure information. One way is to do a make distclean. [EMAIL PROTECTED] amanda-2.4.4p4]$ [EMAIL PROTECTED] amanda-2.4.4p4]$ pkginfo -l SMCgcc PKGINST: SMCgcc NAME: gcc CATEGORY: application ... Can you please help me with some ideas about how to compile this version of amanda on solaris 8? Many gcc installations for Solaris include a script called something like fixheaders. Does your gcc package have such a script and has it been run? [EMAIL PROTECTED] /]# find / -name fixheaders -print [EMAIL PROTECTED] /]# No fixheaders Did you read the part about something like. I did not look up in your documentation what it was called (if it is even there or needed). You should have checked your installation documentation. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
2.4.4p1 compile error on aix 5.2
i had problems about ld when compiling package with gcc 3.3 or xlc.(they were object pointer errors i think - i did not take outputs.) i downloaded the bos.rte.bind_cmds update package from ibm. (which is the package that owns /usr/ccs/bin/ld binary) i applied the patch and recompiled again (without forgetting a make distclean). make finished without error. FYI. -caglar
Compile error 2.4.3 on hp10.20
Hi, I found a problem with compiling the changer-src: I run configure with the following parameters: ./configure --prefix=/opt/local/amanda --program-suffix=2.4.3 --with-user=amanda --with-group=sys --with-config=daily --with-tape-device=/dev/rmt/0n chg-scsi-chio.c: In function `main':chg-scsi-chio.c:644: `conffile' undeclared (first use in this function)chg-scsi-chio.c:644: (Each undeclared identifier is reported only oncechg-scsi-chio.c:644: for each function it appears in.) ggc version 2.8.1 (old I know) I've compiled amanda versions before with this version of gcc without problems I don't need changer support so how do I prevent it from compiling? What am I missing? Henk Martijn ACREO AB Electrum 236 Tel:+46 8 632 7795 S-164 40 KistaFax:+46 8 750 5430 Sweden e-mail: [EMAIL PROTECTED] BEGIN:VCARD VERSION:2.1 X-GWTYPE:USER FN:Henk Martijn TEL;WORK:08-632 77 95 ORG:;Bildgenerering / EIT EMAIL;WORK;PREF:[EMAIL PROTECTED] N:Martijn;Henk X-GWUSERID:henmar END:VCARD
Re: compile error on 2.4.3-20030104
Hi, The newer amidxtaped need the server library which is not build if you set --without-server The fix is not build amidxtaped and amrestore if --without-server is set. The next snapshot will be available soon. Jean-Louis On Thu, Jan 16, 2003 at 02:22:49PM -0800, DK Smith wrote: ###3 Making all in restore-src make[1]: Entering directory `/Admin/Build/amanda-2.4.3-20030104/restore-src' source='amidxtaped.c' object='amidxtaped.o' libtool=no \ depfile='.deps/amidxtaped.Po' tmpdepfile='.deps/amidxtaped.TPo' \ depmode=gcc3 /bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../tape-src -I../server-src -D_FILE_OFFSET_BITS=64 -D_FILE_OFFSET_BITS=64 -O2 -c `test -f 'amidxtaped.c' || echo './'`amidxtaped.c amidxtaped.c: In function `main': amidxtaped.c:478: warning: passing arg 2 of `waitpid' from incompatible pointer type make[1]: *** No rule to make target `../server-src/libamserver.la', needed by `amidxtaped'. Stop. make[1]: Leaving directory `/Admin/Build/amanda-2.4.3-20030104/restore-src' make: *** [all-recursive] Error 1 ./configure \ --without-server\ --prefix=/usr/local_legless/amanda-2.4.3-20030104 \ --with-tmpdir=/tmp/amanda \ --with-includes=/usr/local/gnu/include \ --with-libraries=/usr/local/gnu/lib \ --with-gnutar \ --with-gnutar-listdir=/var/amanda/gnutar-listdir\ --without-amandahosts \ --with-user=amanda \ --with-group=disk \ --with-debugging\ --with-debug-days=4 \ ###3 -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
compile error on 2.4.3-20030104
the last bit of the output: Making all in restore-src make[1]: Entering directory `/Admin/Build/amanda-2.4.3-20030104/restore-src' source='amidxtaped.c' object='amidxtaped.o' libtool=no \ depfile='.deps/amidxtaped.Po' tmpdepfile='.deps/amidxtaped.TPo' \ depmode=gcc3 /bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../tape-src -I../server-src -D_FILE_OFFSET_BITS=64 -D_FILE_OFFSET_BITS=64 -O2 -c `test -f 'amidxtaped.c' || echo './'`amidxtaped.c amidxtaped.c: In function `main': amidxtaped.c:478: warning: passing arg 2 of `waitpid' from incompatible pointer type make[1]: *** No rule to make target `../server-src/libamserver.la', needed by `amidxtaped'. Stop. make[1]: Leaving directory `/Admin/Build/amanda-2.4.3-20030104/restore-src' make: *** [all-recursive] Error 1 ## this is with gcc 3.2 20020903 which is the deault gcc on RH 8.0 distribution. ## I will try another source package...
Re: compile error on 2.4.3-20030104
On Wednesday 15 January 2003 18:07, DK Smith wrote: the last bit of the output: Making all in restore-src make[1]: Entering directory `/Admin/Build/amanda-2.4.3-20030104/restore-src' source='amidxtaped.c' object='amidxtaped.o' libtool=no \ depfile='.deps/amidxtaped.Po' tmpdepfile='.deps/amidxtaped.TPo' \ depmode=gcc3 /bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../tape-src -I../server-src -D_FILE_OFFSET_BITS=64 -D_FILE_OFFSET_BITS=64 -O2 -c `test -f 'amidxtaped.c' || echo './'`amidxtaped.c amidxtaped.c: In function `main': amidxtaped.c:478: warning: passing arg 2 of `waitpid' from incompatible pointer type make[1]: *** No rule to make target `../server-src/libamserver.la', needed by `amidxtaped'. Stop. make[1]: Leaving directory `/Admin/Build/amanda-2.4.3-20030104/restore-src' make: *** [all-recursive] Error 1 ## this is with gcc 3.2 20020903 which is the deault gcc on RH 8.0 distribution. ## I will try another source package... Yes, so would I, I've had no problem building the snapshots with 3.2 as supplied with rh8.0. But I have had kernel downloads go south, and only going after it again will fix the problem for me in that case. I'm out in the boonies on a 56k line thats often 28k or less. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly
compile error on sun 2.5.1
i try to compile amanda 2.4.3 on sun solaris 2.5.1 with gcc 2.95.3 i got error when doing this thing : gcc -g -O2 -o chg-scsi chg-scsi.o scsi-aix.o scsi-changer-driver.o scsi-hpux_new.o scsi-irix.o scsi-linux.o scsi-solaris.o scsi-bsd.o scsi-cam.o sense.o ../server-src/.libs/libamserver.a ../tape-src/.libs/libamtape.a ../common-src/.libs/libamanda.a -lgen -lm -lreadline -ltermcap -lsocket -lns l -lintl Undefined first referenced symbol in file vsnprintf scsi-changer-driver.o ld: fatal: Symbol referencing errors. No output written to chg-scsi collect2: ld returned 1 exit status gmake[1]: *** [chg-scsi] Error 1 gmake[1]: Leaving directory `/export/home/src/amanda-2.4.3/changer-src' gmake: *** [all-recursive] Error 1 thanks, zakki
RE: Compile error, resolution, confusion
I was just about to report the same thing. Amanda 2.4.3b3 would not compile under IRIX 6.5. I came up with the following fix: --- client-src/sendbackup-dump.c.orig Fri Jun 21 01:31:32 2002 +++ client-src/sendbackup-dump.c Fri Jun 21 01:32:31 2002 @@ -215,7 +215,7 @@ dumppid = pipespawn(progname, STDIN_PIPE, dumpin, dumpout, mesgf, xfsdump, - no_record ? -J : skip_argument, + options-no_record ? -J : skip_argument, -F, -l, dumpkeys, -, @@ -241,7 +241,7 @@ program-restore_name = VXRESTORE; dumpkeys = vstralloc(level_str, -no_record ? : u, +options-no_record ? : u, s, f, NULL); @@ -282,7 +282,7 @@ program-restore_name = VRESTORE; dumpkeys = vstralloc(level_str, -no_record ? : u, +options-no_record ? : u, b, f, NULL); @@ -350,7 +350,7 @@ /* AIX backup program */ dumpkeys = vstralloc(-, level_str, -no_record ? : u, +options-no_record ? : u, f, NULL); - - - - - - - - - - - - - - - - - - - - - - - - - - Robert Bottomley | E-mail: [EMAIL PROTECTED] System Administrator | Tel: 909-781-5788 /~\The ASCII College of Engineering | Fax: 909-781-5790 \ / Ribbon Campaign Center for Environmental | CE-CERT X Against Research and Technology | UC Riverside/ \ HTML Email! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Brooks Sent: Monday, June 24, 2002 1:10 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Compile error, resolution, confusion Hello, I have been reading through the archives and found a bit of information that helped me. for amanda 2.4.3b3, I received errors while compiling on a solaris8 (bybee) machine. I applied a change I found in reference to this error, and the compiler error went away. the wierd part: this error didn't happen on different machines running solaris8(bramble), 7, 251, redhat 6.2-7.2, or freebsd3.4. the change was to line 244 of client-src/sendbackup-dump.c: I changed no_record to options-no_record. Interestingly enough, this appears to compile just as well on the other machines too. I have installed on both solaris machines: binutils-2.11.2-sol8-sparc-local bison-1.28-sol8-sparc-local flex-2.5.4a-sol8-sparc-local gcc-3.0.3-sol8-sparc-local libgcc-3.0.3-sol8-sparc-local make-3.79.1-sol8-sparc-local I will include the compiler error messages below. Please note that the biggest difference between the compiling and non-compiling machines is that the non-compiling machine has a slightly older os patch level, Veritas File system and Veritas Volume manager installed, and is a clearcase server. Otherwise, the gcc, binutils, make, etc packages are all the same. What do you all think? --jason the error is: gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c `test -f sendbackup-dump.c || echo './'`sendbackup-dump.c sendbackup-dump.c: In function `start_backup': sendbackup-dump.c:244: `no_record' undeclared (first use in this function) sendbackup-dump.c:244: (Each undeclared identifier is reported only once sendbackup-dump.c:244: for each function it appears in.) make[1]: *** [sendbackup-dump.o] Error 1 make[1]: Leaving directory `/net/jetstream/jetstream1/amanda/bybee/client-src' make: *** [all-recursive] Error 1 -- ~~~ Jason Brooks ~ (503) 641-3440 x1861 Direct ~ (503) 924-1861 System / Network Administrator Wind River Systems 8905 SW Nimbus ~ Suite 255 Beaverton, Or 97008
Compile error, resolution, confusion
Hello, I have been reading through the archives and found a bit of information that helped me. for amanda 2.4.3b3, I received errors while compiling on a solaris8 (bybee) machine. I applied a change I found in reference to this error, and the compiler error went away. the wierd part: this error didn't happen on different machines running solaris8(bramble), 7, 251, redhat 6.2-7.2, or freebsd3.4. the change was to line 244 of client-src/sendbackup-dump.c: I changed no_record to options-no_record. Interestingly enough, this appears to compile just as well on the other machines too. I have installed on both solaris machines: binutils-2.11.2-sol8-sparc-local bison-1.28-sol8-sparc-local flex-2.5.4a-sol8-sparc-local gcc-3.0.3-sol8-sparc-local libgcc-3.0.3-sol8-sparc-local make-3.79.1-sol8-sparc-local I will include the compiler error messages below. Please note that the biggest difference between the compiling and non-compiling machines is that the non-compiling machine has a slightly older os patch level, Veritas File system and Veritas Volume manager installed, and is a clearcase server. Otherwise, the gcc, binutils, make, etc packages are all the same. What do you all think? --jason the error is: gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c `test -f sendbackup-dump.c || echo './'`sendbackup-dump.c sendbackup-dump.c: In function `start_backup': sendbackup-dump.c:244: `no_record' undeclared (first use in this function) sendbackup-dump.c:244: (Each undeclared identifier is reported only once sendbackup-dump.c:244: for each function it appears in.) make[1]: *** [sendbackup-dump.o] Error 1 make[1]: Leaving directory `/net/jetstream/jetstream1/amanda/bybee/client-src' make: *** [all-recursive] Error 1 -- ~~~ Jason Brooks ~ (503) 641-3440 x1861 Direct ~ (503) 924-1861 System / Network Administrator Wind River Systems 8905 SW Nimbus ~ Suite 255 Beaverton, Or 97008
Re: Compile error, resolution, confusion
On Mon, Jun 24, 2002 at 01:10:24PM -0700, Jason Brooks wrote: Hello, I have been reading through the archives and found a bit of information that helped me. for amanda 2.4.3b3, I received errors while compiling on a solaris8 (bybee) machine. I applied a change I found in reference to this error, and the compiler error went away. the wierd part: this error didn't happen on different machines running solaris8(bramble), 7, 251, redhat 6.2-7.2, or freebsd3.4. the change was to line 244 of client-src/sendbackup-dump.c: I changed no_record to options-no_record. I'm only looking at the 2.4.3.b2 code, but I doubt it makes a difference. Certainly your change is not the proper correction. The options identifier I see is a character pointer, not a structure pointer. Also, the no_record parameter should be in scope as an external integer. It is a flag as to whether the no record option is set in the configuration. Check sendbackup.c. In my code, line 55 has the declaration. Check sendbackup.h. In my code, line 65 has the definition. Check sendbackup-dump.c and confirm sendbackup.h is being included. If your correction is valid, there are lots of places around line 244 that should be similarly corrected. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: No working file locking and ruserok compile error
I have searched the config.log file and I see no references to the
string 'ruserok' with regard to the multiply declared ruserok
issue...
That doesn't make any sense. Here's what I see:
configure:14463: checking for ruserok
configure:14491: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include-L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
15
configure:14517: checking for ruserok declaration in netdb.h sys/socket.h libc.h
and so on. In other words, every place ./configure does a test
there should be the same thing in the log along with the actual test
and results. Here's a failure, for instance (Solaris does not have
setmntent):
configure:15096: checking for setmntent
configure:15124: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include-L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
15
Undefined first referenced
symbol in file
setmntent /var/tmp/cccfHbIc.o
ld: fatal: Symbol referencing errors. No output written to conftest
collect2: ld returned 1 exit status
configure: failed program was:
#line 15101 configure
#include confdefs.h
/* System header to define __stub macros and hopefully few prototypes,
which can conflict with char setmntent(); below. */
#include assert.h
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char setmntent();
int main() {
/* The GNU C library defines this for functions which it implements
to always fail with ENOSYS. Some functions are actually named
something starting with __ and the normal name is an alias. */
#if defined (__stub_setmntent) || defined (__stub___setmntent)
choke me
#else
setmntent();
#endif
; return 0; }
You have to do a make distclean first or else the stuff will come from
the cache and you won't see the test results.
I see no reference to the flock tests or any lock tests for that
matter... The only occurrence of the string 'lock' in the config.log
file was inside the word 'block'
Again, this make no sense. Here's the very end of my log:
configure:19342: checking whether posix fcntl locking works
configure:19362: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include-L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
15
In file included from configure:19358:
/home/fortress/a/jrj/work/amanda/amanda-242/common-src/amflock.c:412: warning:
return-type defaults to `int'
If you're not seeing output like this (and you've done a distclean),
I'm not sure what's going on.
CFLAGS=-I/usr/local/include \
LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH \
./configure \
...
Setting LD_LIBRARY_PATH should be a last resort. I think you should be
able to accomplish the same thing setting LIBS, e.g.:
CFLAGS=-I/usr/local/include \
LIBS=-L/usr/local/lib \
./configure \
...
Then you need to look at the configure output to see what it says about
finding readline, e.g. from my system:
checking for readline.h... no
checking for readline/history.h... yes
checking for readline/readline.h... yes
checking for readline in -lreadline... yes
If that doesn't work, you're back to looking at config.log to find out
why the test programs failed.
--with-debug-days=1
Any particular reason you're lowering this value? I'd think you'd want
at least a weekend worth of logs left around.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amanda compile error
amanda.h:1092: conflicting types for `strncasecmp' /usr/include/strings.h:32: previous declaration of `strncasecmp' What is supposed to happen is ./configure should see that you already have a declaration for strncasecmp and disable the Amanda version. For instance, here's what is said on one of my machines: checking for strncasecmp... yes checking for strncasecmp... (cached) yes checking for strncasecmp declaration in string.h strings.h... yes What did it do when you ran it? If you look in config.log for checking for strncasecmp, what's there? Brian Davidson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amanda compile error
I'm trying to build amanda on an NCR 3430 running MP-RAS. While compiling I got the following error: In file included from alloc.c:33: amanda.h:1092: conflicting types for `strncasecmp' /usr/include/strings.h:32: previous declaration of `strncasecmp' make[1]: *** [alloc.lo] Error 1 make[1]: Leaving directory `/home/davidsb/amanda-2.4.3b2-20020308/common-src' make: *** [all-recursive] Error 1 Here are the two conflicting statements: # grep strncasecmp /usr/include/strings.h int strncasecmp(const char *, const char *, size_t); # grep strncasecmp /home/davidsb/amanda-2.4.3b2-20020308/common-src/amanda.h extern int strncasecmp P((const char *s1, const char *s2, int n)); Any clues on what to do beside throw the MP-RAS box out the window (man I really want to do that!). I've only dabbled in C so I'm not very proficient at it. Brian Davidson 11710 Plaza America Drive Reston, Virginia 20190 703.261.4694 703.261.5086 Fax
Re: amanda compile error
Davidson, Brian wrote: I'm trying to build amanda on an NCR 3430 running MP-RAS. While compiling I got the following error: In file included from alloc.c:33: amanda.h:1092: conflicting types for `strncasecmp' /usr/include/strings.h:32: previous declaration of `strncasecmp' make[1]: *** [alloc.lo] Error 1 make[1]: Leaving directory `/home/davidsb/amanda-2.4.3b2-20020308/common-src' make: *** [all-recursive] Error 1 Here are the two conflicting statements: # grep strncasecmp /usr/include/strings.h int strncasecmp(const char *, const char *, size_t); # grep strncasecmp /home/davidsb/amanda-2.4.3b2-20020308/common-src/amanda.h extern int strncasecmp P((const char *s1, const char *s2, int n)); Change 'int n' to 'size_t n' here. Any clues on what to do beside throw the MP-RAS box out the window (man I really want to do that!). I've only dabbled in C so I'm not very proficient at it. I think I might be tempted to defenestrate it myself. :) Brian Davidson 11710 Plaza America Drive Reston, Virginia 20190 703.261.4694 703.261.5086 Fax
Re: Compile error
--- Thomas Hepper [EMAIL PROTECTED] wrote: Hi, On Thu, Feb 14, 2002 at 03:00:00PM +, Robert Early wrote: Hi, I;m getting the following compile error when trying to compile amanda amanda-2.4.3b2: gcc -D_FILE_OFFSET_BITS=64 -g -O2 -o chg-scsi-chio chg-scsi-chio.o scsi-hpux.o scsi-chio.o ../server-src/.libs/libamserver.a ../tape-src/.libs/libamtape.a ../common-src/.libs/libamanda.a -lgen -lm -ltermcap -lnsl -lcur_colr /usr/ccs/bin/ld: Unsatisfied symbols: config_dir (data) collect2: ld returned 1 exit status *** Error exit code 1 Any ideas? Which OS, which configure flags ?? It's HPUX 11.0, with the following configure flags: configure --with-user=amanda --prefix=/opt/amanda --localstatedir=/var/opt --with-configdir=/etc/opt/amanda --with-amandahosts --with-group=sys Robert. __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
Re: Compile error
Hi, On Thu, Feb 14, 2002 at 03:00:00PM +, Robert Early wrote: Hi, I;m getting the following compile error when trying to compile amanda amanda-2.4.3b2: gcc -D_FILE_OFFSET_BITS=64 -g -O2 -o chg-scsi-chio chg-scsi-chio.o scsi-hpux.o scsi-chio.o ../server-src/.libs/libamserver.a ../tape-src/.libs/libamtape.a ../common-src/.libs/libamanda.a -lgen -lm -ltermcap -lnsl -lcur_colr /usr/ccs/bin/ld: Unsatisfied symbols: config_dir (data) collect2: ld returned 1 exit status *** Error exit code 1 Any ideas? Which OS, which configure flags ?? Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
Compile error
Hi, I;m getting the following compile error when trying to compile amanda amanda-2.4.3b2: gcc -D_FILE_OFFSET_BITS=64 -g -O2 -o chg-scsi-chio chg-scsi-chio.o scsi-hpux.o scsi-chio.o ../server-src/.libs/libamserver.a ../tape-src/.libs/libamtape.a ../common-src/.libs/libamanda.a -lgen -lm -ltermcap -lnsl -lcur_colr /usr/ccs/bin/ld: Unsatisfied symbols: config_dir (data) collect2: ld returned 1 exit status *** Error exit code 1 Any ideas? Robert. __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
Re: No working file locking and ruserok compile error
Take a look at config.log and see why the test programs are failing. It might even be the ruserok() problem. B) When I compile on OSF/1 v5.1 (or DEC ALPHA, or Tru64), I get an error about ruserok being declared twice... I am using a gnu make 3.79 and gcc 3.0.3. Can I comment out the ruserok declaration in amanda.h with no adverse effects? In theory, the declaration in amanda.h is only enabled if ./configure did **not** find a declaration in a certain set of system header files. Where is the second (system) declaration on your system? This may just be a matter of adding another header file to the list or fixing a test program. Again, look for what happened in config.log. I have searched the config.log file and I see no references to the string 'ruserok' with regard to the multiply declared ruserok issue What other information could I provide about the ruserok issue? What can I do to debug it, other than the config.log file? and... I see no reference to the flock tests or any lock tests for that matter... The only occurrence of the string 'lock' in the config.log file was inside the word 'block' Where else can I look to see why the configure script is not finding evidence of file locking on a OSF/1 v5.1 Unix system? ## Since this is a proprietary vendor supplied distribution -- unlike the GNU distribution -- readline was also missing. So, since I thought this to be an easy fix, I built and installed readline, however subsequent runs of the AMANDA configure script did not pick it up... Maybe someone can make a suggestion to make it work? Here is what I am doing to set the environment in which configure runs: CFLAGS=-I/usr/local/include \ LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH \ ./configure \ --prefix=/usr/local/amanda-2.4.2p2 \ --without-amandahosts \ --with-user=amanda \ --with-group=operator \ --with-configdir=/usr/local/etc/amanda \ --with-tmpdir=/tmp/amanda \ --with-debugging\ --with-debug-days=1 \ previous to the above invocation: CFLAGS was undefined LD_LIBRARY_PATH=/usr/local/gcc-3.0.3/lib The readline hdr files and lib were/are here: /usr/local/include/readline/*.h /usr/local/lib/libreadline.a Thanks to all in this wonderful community May all your backups be bit-perfect.
Re: No working file locking and ruserok compile error
I have searched the config.log file and I see no references to the
string 'ruserok' with regard to the multiply declared ruserok
issue...
That doesn't make any sense. Here's what I see:
configure:14463: checking for ruserok
configure:14491: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include-L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
15
configure:14517: checking for ruserok declaration in netdb.h sys/socket.h libc.h
and so on. In other words, every place ./configure does a test
there should be the same thing in the log along with the actual test
and results. Here's a failure, for instance (Solaris does not have
setmntent):
configure:15096: checking for setmntent
configure:15124: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include-L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
15
Undefined first referenced
symbol in file
setmntent /var/tmp/cccfHbIc.o
ld: fatal: Symbol referencing errors. No output written to conftest
collect2: ld returned 1 exit status
configure: failed program was:
#line 15101 configure
#include confdefs.h
/* System header to define __stub macros and hopefully few prototypes,
which can conflict with char setmntent(); below. */
#include assert.h
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char setmntent();
int main() {
/* The GNU C library defines this for functions which it implements
to always fail with ENOSYS. Some functions are actually named
something starting with __ and the normal name is an alias. */
#if defined (__stub_setmntent) || defined (__stub___setmntent)
choke me
#else
setmntent();
#endif
; return 0; }
You have to do a make distclean first or else the stuff will come from
the cache and you won't see the test results.
I see no reference to the flock tests or any lock tests for that
matter... The only occurrence of the string 'lock' in the config.log
file was inside the word 'block'
Again, this make no sense. Here's the very end of my log:
configure:19342: checking whether posix fcntl locking works
configure:19362: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include-L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
15
In file included from configure:19358:
/home/fortress/a/jrj/work/amanda/amanda-242/common-src/amflock.c:412: warning:
return-type defaults to `int'
If you're not seeing output like this (and you've done a distclean),
I'm not sure what's going on.
CFLAGS=-I/usr/local/include \
LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH \
./configure \
...
Setting LD_LIBRARY_PATH should be a last resort. I think you should be
able to accomplish the same thing setting LIBS, e.g.:
CFLAGS=-I/usr/local/include \
LIBS=-L/usr/local/lib \
./configure \
...
Then you need to look at the configure output to see what it says about
finding readline, e.g. from my system:
checking for readline.h... no
checking for readline/history.h... yes
checking for readline/readline.h... yes
checking for readline in -lreadline... yes
If that doesn't work, you're back to looking at config.log to find out
why the test programs failed.
--with-debug-days=1
Any particular reason you're lowering this value? I'd think you'd want
at least a weekend worth of logs left around.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
No working file locking and ruserok compile error
Two issues I need some perspective on... A) What should I do about warnings regarding an absence of file locking Could this create run-time problems and be a hindrance to success? checking disk device prefixes... /dev/ - /dev/r checking whether posix fcntl locking works... no checking whether flock locking works... no checking whether lockf locking works... no checking whether lnlock locking works... no configure: warning: *** No working file locking capability found! configure: warning: *** Be VERY VERY careful. B) When I compile on OSF/1 v5.1 (or DEC ALPHA, or Tru64), I get an error about ruserok being declared twice... I am using a gnu make 3.79 and gcc 3.0.3. Can I comment out the ruserok declaration in amanda.h with no adverse effects? Uhm: Note to maintainers... the .3beta builds on source forge fail worse on the Alphas compared to this trivial ruserok issue on the 2.4.2p2 build. jfk@host gcc -v Reading specs from /usr/local_cci/gcc-3.0.3/lib/gcc-lib/alphaev67-dec-osf5.1/3.0.3/specs Configured with: ../gcc-3.0.3/configure --prefix=/usr/local_cci/gcc-3.0.3 --enable-languages=c,c++,f77 Thread model: single gcc version 3.0.3 jfk@host ./configure \ --without-server\ --prefix=/usr/local/amanda-2.4.2p2 \ --with-user=amanda \ --with-group=operator \ --with-tmpdir=/tmp/amanda \ --with-debugging\ --with-debug-days=1 . . . . creating server-src/Makefile creating server-src/amstatus.pl creating tape-src/Makefile creating config/Makefile creating Makefile creating config/config.h jfk@host make Making all in config make[1]: Entering directory `/net/Admin/Build/amanda-2.4.2p2/config' make[1]: Leaving directory `/net/Admin/Build/amanda-2.4.2p2/config' Making all in common-src make[1]: Entering directory `/net/Admin/Build/amanda-2.4.2p2/common-src' /usr/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src-g -O2 -c alloc.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -g -O2 -c alloc.c -o alloc.o In file included from alloc.c:33: amanda.h:947: conflicting types for `ruserok' /usr/local/gcc-3.0.3/lib/gcc-lib/alphaev67-dec-osf5.1/3.0.3/include/unistd.h:714: previous declaration of `ruserok' make[1]: *** [alloc.lo] Error 1 make[1]: Leaving directory `/net/Admin/Build/amanda-2.4.2p2/common-src' make: *** [all-recursive] Error 1
Re: No working file locking and ruserok compile error
A) What should I do about warnings regarding an absence of file locking Fix them :-). Could this create run-time problems and be a hindrance to success? Yes. Very much so. Take a look at config.log and see why the test programs are failing. It might even be the ruserok() problem. B) When I compile on OSF/1 v5.1 (or DEC ALPHA, or Tru64), I get an error about ruserok being declared twice... I am using a gnu make 3.79 and gcc 3.0.3. Can I comment out the ruserok declaration in amanda.h with no adverse effects? In theory, the declaration in amanda.h is only enabled if ./configure did **not** find a declaration in a certain set of system header files. Where is the second (system) declaration on your system? This may just be a matter of adding another header file to the list or fixing a test program. Again, look for what happened in config.log. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amanda compile error on solaris
There are quite few lines proceeding with #line in uparse.c files. Besdies
the line mentioned below, there is another one referencing to bison.simple.
Are these lines use by a parser? Or just comment lines?
What I did actually to get around this problem was to comment out all lines
proceeding with #line with /* */.
It compiled ok. Did I do the right thing?
- Original Message -
From: Alexandre Oliva [EMAIL PROTECTED]
To: Howard Zhou [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, May 27, 2001 2:41 PM
Subject: Re: amanda compile error on solaris
On May 26, 2001, Howard Zhou [EMAIL PROTECTED] wrote:
/home/gandalf/u66/jrj/work/amanda/amanda-242/recover-src/uparse.y:32:
Edit uparse.c and remove all pathname components in any occurrences of
the filename above, leaving just `uparse.h'. This should fix the
problem.
JJ, this is yet another trick related with building release tarballs:
it's best done in a copy of the source tree after `make
maintainerclean' (I believe this will remove uparse.c and any other
lex/yacc-generated files).
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: amanda compile error on solaris
On May 28, 2001, Howard Zhou [EMAIL PROTECTED] wrote:
Are these lines use by a parser? Or just comment lines?
They're mostly used to emit debugging information, so that the object
file points at the original file, as opposed to the generated file.
However, the preprocessor also uses these notes to look for headers
mentioned in `#include header.h' directives (compare with `#include
header.h', that causes the preprocessor to search only the default
search path, not do relative search).
What I did actually to get around this problem was to comment out all lines
proceeding with #line with /* */.
It compiled ok. Did I do the right thing?
Yep, that works.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: amanda compile error on solaris
On May 26, 2001, Howard Zhou [EMAIL PROTECTED] wrote:
/home/gandalf/u66/jrj/work/amanda/amanda-242/recover-src/uparse.y:32:
Edit uparse.c and remove all pathname components in any occurrences of
the filename above, leaving just `uparse.h'. This should fix the
problem.
JJ, this is yet another trick related with building release tarballs:
it's best done in a copy of the source tree after `make
maintainerclean' (I believe this will remove uparse.c and any other
lex/yacc-generated files).
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
amanda compile error on solaris
Hi, I am trying to install amanda on a solaris system and got the following error with either make or gmake. _FILE_OFFSET_BITS=64 -g -O2 -c set_commands.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../client-src -I../tape-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c uparse.c /home/gandalf/u66/jrj/work/amanda/amanda-242/recover-src/uparse.y:32: amanda.h: Permission denied /home/gandalf/u66/jrj/work/amanda/amanda-242/recover-src/uparse.y:33: amrecover.h: Permission denied *** Error code 1 make: Fatal error: Command failed for target `uparse.o' Current working directory /usr/cvs/ftp/amanda-2.4.2p2/recover-src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Any help in this regards will be highly appreciated. Thanks. Howard
Re: gnuplot compile error
Hi, hen I tried to install gnuplot with make, I got the following errors. Can someone help me on this issue? It seems to me that gnuplot needs GD to install, and GD will need libzip, ligjpeg and libpng (or lib gif)... Gnuplot is typical sintalation that requires bunch of pre installation. You CAN run Amanda without Gnplot, only you won't have the graphical output. About AMplot, one question, I did not yet took time to look at the code too closely, but would it be possible to add an option to amplot that would sepcify the type of terminal? I often check tre report from home throught telnet, using a telnet client that includes a Tek401x emulator. Amplot works fine on it (fine and fast) but I have to patch by hand amplot.awk to do that. Best regards, Olivier
Re: Compile error?
They look installed. Try forcing make to rebuild uscan.c from uscan.l: touch recover-src/uscan.l Robert L. Harris John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: sst compile error
Matt, if you have Solaris 8 you don't need SST at all. Solaris 8 includes a generic SCSI driver. Does it require you to be running as root like (an unpatched) sst? If so, that won't work very well with Amanda which tries to run as root as little as possible. Joe Rhett John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: sst compile error
flash:/usr/src/amanda-2.4.2-19991216-beta1/contrib/sst# make gcc -D_KERNEL -c sst.c sst.c: In function `sst_handle_sense': sst.c:2103: warning: passing arg 1 of `timeout' from incompatible pointer type ... sst.c:2451: `__builtin_va_alist' undeclared (first use in this function) ... How do I fix this Here's what I've posted in the past: Go to the mailing list archives and search for "Just can't build sst". There is a long, involved, exchange from last December about this. The short answer is that you can build with gcc, but I don't recall anyone saying the final result worked (not that it didn't, just no confirmation). Mike Taylor John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Compile error?
I've built amanda so far on about 6 clients. On # 7 I'm getting this: gcc -g -o .libs/amrecover amrecover.o display_commands.o extract_list.o help.o set_commands.o uparse.o uscan.o -ll -R/usr/local/lib ../client-src/.libs/libamclient.so -lgen -lm -ltermcap -lsocket -lnsl -lintl -R/usr/local/lib ../tape-src/.libs/libamtape.so -lgen -lm -ltermcap -lsocket -lnsl -lintl -R/usr/local/lib ../common-src/.libs/libamanda.so -lgen -lm -ltermcap -lsocket -lnsl -lintl -lgen -lm -ltermcap -lsocket -lnsl -lintl Undefined first referenced symbol in file yy_scan_string uscan.o ld: fatal: Symbol referencing errors. No output written to .libs/amrecover *** Error code 1 make: Fatal error: Command failed for target `amrecover' Current working directory /home/roharris/Amanda/amanda-2.4.1p1/recover-src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Anyone seen this? Robert -- :wq! --- Robert L. Harris| Micros~1 : Unix System Administrator |For when quality, reliability at Agency.com | and security just aren't \_ that important! DISCLAIMER: These are MY OPINIONS ALONE. I speak for no-one else. FYI: perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
