How to use the bootstrap.dat in Mavericks? So I'm trying to sync with the network in Bitcoin-Qt, but I just can't seem to make use of the bootstrap.dat file that I downloaded, which is annoying because it will be awfully slow to sync without it.

There was no folder in Application Support where the file was supposed to go, so I made one: 

User/Library/Application Support/Bitcoin - and put the bootstrap.dat file in there.

Yet still when I launch Bitcoin-Qt it fails to use the bootstrap, and just tries to sync normally.

Does anyone know if I'm doing something wrong here? Or if there's a way around this problem?

I'm running OSX 10.9 Mavericks.

Thanks
I can at least tell you what I did, on my iMac running OS X 10.9.1 (Mavericks).


I ran Bitcoin-Qt, which immediately started synching.  I could see by the progress bar that if it's roughly linear, it would take 8 - 10 days to complete.  The nice thing about it was that I could see the directories it needed by what it created for itself in ~/Library/Application Support
I downloaded the bootstrap.dat.torrent file from sourceforge.net
Installed the deluge torrent app (deluge-torrent.org), and ran that to expand the bootstrap.dat file (I had never used the BitTorrent protocol before -- was pretty straightforward.).  It put the result in my home directory (14222116865 bytes).
Quit the still laboring Bitcoin-Qt ... then renamed its directory so I could see what directories it required, and in case I had to go back to pick up where I left off:

cd ~/Library/Application\ Support; mv Bitcoin BC_save
Manually created the same directories so I'd have a place to put the bootstrap.dat file

find BC_save -type d -print   # See what dirs are needed

mkdir -p Bitcoin/blocks/index; mkdir Bitcoin/blocks/chainstate


(Later Qt creates Bitcoin/blocks/database, but it wasn't there at this point.)
I'm surprised that more than just "mkdir Bitcoin" is necessary, but apparently you already tried that, so...)


Started up Bitcoin-Qt again.  It immediately "adopted" the directories I had created, and new files were appearing (e.g., wallet.dat).  The lower-left edge had a message indicating it was reading a file from the disk -- so it appeared to be working.
An overnight run -- and it's already done.