Conor,
What's your environment? Are you running OSX? I assume so, because I assume you are running the commands in a terminal window.
Conor Quinn wrote:
--- Glen Mazza <[EMAIL PROTECTED]> wrote:
Did you build (compile) the application first? If you just downloaded the source (instead of the binary) version of FOP, you'll need to build the app first by typing "ant" (or "build.sh") at the command line in the root directory.
I have definitely downloaded the fop-0.20.5-bin.tar.gz file, and not the source version. I would like to try out Ant soon, but I'm still wondering what my problem with the binary version is. I suspect that I've just missed something very basic in how I structure my directory. As it stands, I just have the above file unpacked with StuffIt---oddly and perhaps significantly, the suggested tar -xzf approach made it cranky:
gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error exit delayed from previous errors
What happens if you try tar tvf fop-0.20.5-bin.tar ? Do you get a list of files without error messages?
...because even with StuffIt turned off, a download still just gets me a straight fop-0.20.5-bin.tar on the Desktop, not fop-0.20.5-bin.tar.gz.
Unless I'm missing something, though, I don't think the file truncation issue is what's going on, and so I just have said tar unarchived with StuffIt and plopped on the Desktop directory as a plain folder directory ("fop-0.20.5").
Perhaps, then, this is the problem? While Apache just says to unarchive the tar into a "directory/folder that is convenient on your system," is there perhaps some further step involved in placing specific files in specific places that I have missed?
Regarding Peter's suggestion, i.e.
have you tried fop.sh fonts.fo fonts.pdf ?
trying that I got a similar response:
-bash: fop.sh: command not found
Again, it seems that somehow I'm not managing to get the fop command into an accessible position. Any suggestions? Thanks for your help so far!
Bash finds commands using the PATH variable. Non-root users will generally have the current directory (.) appended to the PATH. This can be examined by
echo $PATH
If there is no '.' in your path, bash would not have found fop.sh. If your current directory ( 'pwd' will show it ) was not the directory containing fop.sh, bash would not have found it anyway. If the file fop.sh is not executable, bash would not have been able to run it. What happens when you cd into the directory in which the tarball was untarred, and execute
ls -l fop.sh
What happens if you execute ./fop.sh fonts.fo fonts.pdf
Peter -- Peter B. West <http://cv.pbw.id.au/>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
