after downloading the tarball to a directory and making that directory your current working directory...
<b>EXACTLY</b> what commands did you run?

I know this has already been asked, but you did extract the tarball and cd into the directory didn't you?

I know this has already been asked, but you did extract the tarball and cd into the jigdo-xxx directory didn't you?

Actually llama_meme that's where it gets a little weird. As any of you know who use Macs in any version of Mac OS it uses a proprietary file system called hfs and in version Mac OS 8.0 or higher (I may be wrong, it may be Mac OS 8.1 or higher) they use an updated version of the file system called hfs+. This very same file system is also used in any version of Mac OS X to date even though Mac OS X is based on freebsd underpinnings (and of course normally freebsd uses a more native file system such as ext2 or ext3). As a direct result of this even though in the terminal application one could browse to /desktop (same as that user's Mac OS X gui desktop folder), I have found that for some reason unknown to me it's not possible for a technical reason (again I really don't know why) folders the user creates on their desktop (same as /desktop folder) don't seem to be browsable in the terminal. In other words you can browse to /desktop in the terminal application, but then when I try to go to the Download directory I created on my desktop for downloaded files by typing cd /download while in my desktop's directory (same as /desktop) I get some sort of error (I have forgotten which error I got since trying this) saying it's not possible to do so. I need a way to get to this Download directory on my desktop since that's where I extracted the Jigdo source tarball to.

type
cd download
while in your desktop directory. Not
cd /download

Alex

I just tried that and got this error: download: No such file or directory.

#while in desktop
pwd
#then
ls -l

# Post the ouput please

The response I get from pwd is /Desktop and ls -l simply outputs nothing and I'm returned to the command prompt.

Okay guys I finally figured this out after reading the help file for Terminal and it said I could drag the actual folder into the Terminal app to find its path and low and behold in turns out that to get to just that one directory the path is /Users/craigdav/Desktop/Download/ to have the Terminal cd to /desktop/Download/. I think the reasoning behind this is that Apple's gui is mearly meant to cover up the actual path so people feel right at home for those who used Mac OS 9.2.2 or earlier or Windows so they would feel at home and not be paranoid about switching to Mac OS X. By the way I just tried to install Jigdo from source since I now know the technical path, but when I ran ./configure I was informed I needed to install libdb3 so I need to know where to download the source from and how to install it (just list the commands in the order I should run them).

I have now found the libdb3 source, but after I did configure and make (which seemed to work fine) when I tried to make install it outputted mkdir: /usr/local/BerkeleyDB.4.1: No such file or directory
make: *** [install_setup] Error 1. Why am I getting this error and what do I need to do to get rid of it?

I now have additional info to add. I just called Apple's tech support yesterday and they said if I have the Apple Developer's Tools installed (which I do) I should have libdb3 installed. It still seems somewhat odd that they say that since whenever I try to run Jigdo's ./configure I get an error along the lines of libdb3 not being installed, yet I know that's not true. Also the readme specifically asks me to run ./configure with these parameters: ./configure --without-gui && make. I know this doesn't make a difference as I get the same libdb3 error when running ./configure without any special parameters. If anyone knows what's causing this error maybe I could get this to work. I'm not sure about this myself, but if the Apple Developer Tools installs libdb3 into directories other than the Unix defaults that may be causing the problem. Thanks for all your help so far everyone.

I have new info to add that may help with the diagnosis of the situation. First I managed to find out that other people are experiencing the same compiling error I'm, but with different software and apparently it only affects Mac OS X and the case I found was using 10.1.5. As a result of compile problems experienced by people besides myself I switched to the binary release of Jigdo and it worked well until I got an error code. Here's the error: jigdo-file failed with code 126 - aborting. Hopefully others have experienced the error and can help. Also Fink users have reported gcc compile problems with version 3.3 and apparently bugs still affect 3.1 as well (not sure why) so I'm not suprised by the compile problems upon learning this.

I've just learned after doing a Google search that for the Jigdo 0.6.8 source to compile on freebsd a diff must be applied. I 've never used a diff before so I will need detailed instructions for the command syntax.