[tpitts1]

When I try to install the Project builder package from the ADC site, it says that it can not write bom to path. It says try to install again, and I try to no avail, b/c it then hangs up. Is there a way to install it from the terminal? Has anyone else had this problem.

I really need these tools for my C programming classes.

[mcgritch]

The problem is likely due to the fact that you expanded with StuffIt in OSX. Try and decompress with gnutar -zxvf or tar -xvf, or boot into OS9 and use StuffIt there, then double-click Developer.pkg to install. This issue has appeared in other threads; I had the same problem and gnutar worked for me.

See previous thread:
http://forums.macnn.com/cgi-bin/Foru...ML/000131.html

Good luck.

Originally posted by tpitts1:
When I try to install the Project builder package from the ADC site, it says that it can not write bom to path. It says try to install again, and I try to no avail, b/c it then hangs up. Is there a way to install it from the terminal? Has anyone else had this problem.

I really need these tools for my C programming classes.

[This message has been edited by mcgritch (edited 12-03-2000).]

Actually, I just went through this whole problem of un-tar-ing the Developer Tools download (the 97.7MB tar file). There are several issues:

1) If you use a browser to download the files (such as IE 5 beta that came with OSXPB, you need to set the "File Helpers" preference for .tar files to just "save to disk" rather than post-process with stuffit expander or some other tool. Otherwise you get some weird stuff (like partially expanded tar files, and the error message where it says "Could not install BOM to path") There's nothing wrong with using a browser for downloading, just make sure it's set to just download and nothing more.

2) After talking to Apple Developer Support on the phone, they sent me a message saying I needed to use the following command in the terminal to expand the .tar file:

gnutar -zxvf filename (where filename is the .tar archive)

This is confusing, since, as someone previously posted, usually one would just type gnutar -xf (or xvf). It turns out this gnutar will return an error when trying to un-tar the DeveloperTools .tar file unless the -z option is used as well. I imagine, although this is just a guess, that this has to do with the compression scheme used for the tar file. I couldn't quite tell from the man pages for it.

Anyhow, the above works, for whatever reasons. After doing this, you should get a .pkg installer, which should then have no problems with the installation.

This was all a bit of a pain in the ass, and could have been avoided if Apple would simply post a readme/instructions file on their software downloads area. Either that or using a different compression format (zip would probably have been just fine, no?)

-Dave

[tpitts1]

Thanks for the info, especially for the future readers of this post. However, I have moved way beyond that problem(originally posted 12-3-2000)

I may be wrong but the reasons for the different compression options on the command line have to do with "exactly" what type of archive you are decompressing.

tar files use different options than say...gnutar files. Some files are even double compressed and that may be one of your other reasons.
If you do a
man tar
or
man gnutar
in the terminal window, then you will get to different sets of instructions, even though the two programs work in pretty much the same way.
The reason that .zip files are not as prevalent, or why Apple chose not to offer them that way is b/c the Unix world uses mostly the aforementioned utilities. Most Unix machines do carry an unzip utility, though I have not tested on this OS yet.