silvert@cs.dal.ca (Bill Silvert) (01/09/90)
It was great to get the LHARC sources, and they compile without any
problem on BSD 4.3, but I need help porting them to Sys V. Can anyone
steer me to a source of the routines mkdir(), rmdir(), rename() and
ftruncate()? All but ftruncate() seem self-explanatory, but the code is
pretty obscure and I imagine that there must be others out there who have
run into this problem.
--
Bill Silvert, Habitat Ecology Division.
Bedford Institute of Oceanography, Dartmouth, NS, Canada B2Y 4A2
UUCP: ...!{uunet,watmath}!dalcs!biomel!bill
Internet: bill%biomel@cs.dal.CA BITNET: bill%biomel%dalcs@dalacgjh@otter.hpl.hp.com (Graham Higgins) (01/10/90)
> a source of the routines mkdir(), rmdir(), rename() and > ftruncate()? All but ftruncate() seem self-explanatory, but the code is ftruncate is a U**x kernel routine and will have to be simulated, the others should be available via library utilities (dirent.h?, dir.h?), Steven Grimm reports that the sources compiled up OK under BSD, so try the libBSD option, if you have one. Graham ====== ------------------------------------------------------------------ Graham Higgins | Phone: (0272) 799910 x 24060 Hewlett-Packard Labs | gray@hpl.hp.co.uk Bristol | gray%hplb.uucp@ukc.ac.uk U.K. | gray@hplb.hpl.hp.com ------------------------------------------------------------------ Disclaimer: My opinions above are exactly that, mine and opinions. ------------------------------------------------------------------
bammi@dsrgsun.ces.CWRU.Edu (Jwahar R. Bammi) (01/11/90)
to anyone who may be interested: the LHARC sources recently posted
compiles and runs just fine under TOS when compiled with tos-Gcc. Some
minor adjustments were needed (for 16/32 bit ints), ftruncate() was
pretty easy to simulate. the resulting code is a little smaller than
the Lharc that was posted to comp.binaries.atari.st, and it runs much
quicker too (though its no speed demon, due to the way lzhuf.c is
coded). Unlike the Lharc for St that was posted, and the recently
posted unlzh12, this one handles path names, creating folders etc
correctly. i personally still prefer zoo.
bill shroka (our local archives expert) is currently looking into
speeding up things. he also did an excellent port of zoo to Gcc. his
port is sigificantly faster than the turbo-c compiled one that was
posted to the net, and has all the extra St features also implemented.
--
bang: {any internet host}!dsrgsun.ces.CWRU.edu!bammi jwahar r. bammi
domain: bammi@dsrgsun.ces.CWRU.edu
GEnie: J.Bammi