🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

2 total messages Started by Egan F. Ford Fri, 11 Sep 1992 18:25
tar 1.11
#819
Author: Egan F. Ford
Date: Fri, 11 Sep 1992 18:25
60 lines
2655 bytes
I have an SCO 3.2.4 with 3.2.4 Dev and gcc 2.2.2.  After ./configure
--prefix=/usr/gnu and setting in the Makefile -traditional -D_NO_PROTOTYPE 
-D_KR -D_SVID I got the thing to start to compile until gnu.c then I get 
the error:

parse error before `const'
gnu.c:289: syntax error before `void'
gnu.c:290: syntax error before `void'
gnu.c:291: parse error before `{'
gnu.c:294: warning: initialization of `frst' makes integer from pointer
withoutt
gnu.c:294: initializer element for `frst' is not constant
gnu.c:295: warning: initialization of `scnd' makes integer from pointer
withoutt
gnu.c:295: initializer element for `scnd' is not constant
gnu.c:297: parse error before `return'
gnu.c: In function `get_dir_contents':
gnu.c:427: `dirent_cmp' undeclared (first use this function)
gnu.c:427: (Each undeclared identifier is reported only once
gnu.c:427: for each function it appears in.)
gmake: *** [gnu.o] Error 1

So I tryed "gmake CC=cc".  errors:

bison -y  getdate.y             (also tryed yacc and yacc -Sw600)
conflicts:  9 shift/reduce
mv -f y.tab.c getdate.c
cc -c -g  -DMAJOR_IN_SYSMACROS=1 -DDIRENT=1 -DNO_REMOTE=1 -DSTDC_HEADERS=1...
getdate.c
cc -g -o tar tar.o create.o extract.o buffer.o getoldopt.o update.o gnu.o...
mangl 
ld: Symbol valloc in malloc.o is multiply defined. First defined in port.o
gmake: *** [tar] Error 1
rm  getdate.c

Sooo... I tryed removing valloc in port (I tryed malloc later) and then
gmake CC=cc.  errors:

undefined                       first referenced
 symbol                             in file
alloca                              getopt.o
ld fatal: Symbol referencing errors. No output written to tar
gmake: *** [tar] Error 1

So I add alloca.c to SRC and alloca.o OBJ in the Makefile and
gmake CC=cc.  no errors.

tar appears to create .tar and .tar.Z archives very well, and to tar Ztvf.
However when creating a tar archive using cvf you get L\001\004 as the output 
for each file name.  When using tar xvf or xf, many of the files pipe to 
stdout and fails to restore the files.

I hope this helps.  If you have any help I'd appreciate it.

Thanks.

-- 
Egan F. Ford
uunet!cbs!egan      
upl.com!neb!cbs!egan
tar 1.11
#846
Author: Michael I Bushnell
Date: Mon, 14 Sep 1992 14:39
18 lines
1234 bytes
   Resent-Date: Fri, 11 Sep 92 12:25:45 MDT
   Date: Fri, 11 Sep 92 12:25:45 MDT
   From: Egan F. Ford <egan@upl.com>
   Sender: gnulists@ai.mit.edu
   X-Mailer: ELM [version 2.3 PL11]
   Resent-From: bug-gnu-utils-request@prep.ai.mit.edu

   I have an SCO 3.2.4 with 3.2.4 Dev and gcc 2.2.2.  After ./configure
   --prefix=/usr/gnu and setting in the Makefile -traditional -D_NO_PROTOTYPE 
   -D_KR -D_SVID I got the thing to start to compile until gnu.c then I get 
   the error:

You should not have used -traditional, or the other options.
Configure should correctly figure out the options to use, or it has a
bug.  You should never need to edit the Makefile produced by GNU
programs which come with configure.

	-mib
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads