|
|
How do you compile it - Explanation and Solution
Like many source code distributions, cdrecord comes with a file INSTALL describing how to compile and install the sources. Unfortunately Apple went with HFS+ as preferred File System, effectively crippling MacOS X as to not distinguish upper and lower case in filenames.
What is happening? The first default rule for make is to look if the target (install, in this case), already exists. Because of this you could have a file called project.c, and compile it by typing make project. As long as project.c is newer than the file project, make would call the C compiler with the default arguments to recompile your just-edited file. When called with make install, the make command will first look for a file called install, and, because of HFS+, find any capitalisation of that as well. (iNsTaLL, install, INSTALL, ... all match install) If any such file exists, make assumes there is nothing left to do. If there were no such file, make would next look for a rule (in the makefile) called 'install' and do what is written there.
How do you compile it - Explanation and Solution
If you only need UFS for compiling, do what I did, create a UFS image with Disk Copy. The image will be read/write but before you can put anything in it, you have go into Get Info and change the file permissions (by default the mounted image is owned by system and group "wheel" has only read access). When you're done compiling you can delete the contents of the image file and unmount it so it's clean for the next time (make sure to Empty Trash before unmounting). |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.08 seconds |
|