Search results

If you get to grips with command-line substitution that might help. For example replacing "Disk2" with "Disk3" in the previous command: du -dh /Volumes/Disk2/data ^Disk2^Disk3

Classic and Carbonized for OS X. From the MacSoft website:

Only if you install XCode (Apple Developer Tools). It's not included with the Operating System.

Try resetting the NVRAM as described in this Apple document. Short version: at the OF prompt type: reset-nvram reset-allYour mac should restart.

Did you try the suggestion from the warnings shown above? W: You may want to run apt-get update to correct these problems

Can you post the output of "nvram -p" here and we'll have a look.

The auto-boot setting in your NVRAM might be wrong - try this in a terminal window: sudo nvram 'auto-boot?'='true' and then see what happens when you reboot.

Add "-lz" to your LDFLAGS: LDFLAGS=-L/usr/local/Coral/lib -lcoral -lpcap -lhashtab -lz -lstdc++

Try moving /Library/Receipts/X11User.pkg to the trash and see if the installer works.

The arguments you're passing to gcc aren't quite right. You use the "-I" flag to specify directories to search for include files, and "-L" to specify directories to search during the link stage for libraries. So your command should be: gcc -I/usr/include -o fnf.tgt fnf.c...

Rather than building all the required libraries etc. by hand, consider using Fink or MacPorts (formerly Darwin Ports) to get the required libraries etc. They're already either in binary form ready to install, or in code already configured to compile cleanly on OS X. I've installed gtk+, atk...

Hi Javier - It's part of the BSD subsystem, so if you have your original OS X install disks handy, grab the BSD.pkg file from it, open it with Pacifist and extract the usr/bin/install file. I'd recommend that rather than re-installing the entire BSD subsystem, which may revert other files to...

You need to find where routines such as ilv_const_pin() etc. are. For example if they're in a library file that's built before fnf.tgt, that library needs to be used when linking the target app (e.g. gcc -o fnf.tgt fnf.o -L. -livllib or something). Or provide the source files directly if that...

Add the following to ~/.bashrc (creating the file if it doesn't exist): export PATH=/usr/local/bin:$PATHOpen a new terminal window and you should be all set.

You're welcome :)

This is a good point, but the output of the OP's cron job indicates that it is the current user's crontab entry:

It depends of course on what that simple .c file depends on. For example, hnbucket appears to be part of a hash table algorithm. Do you have a separate file which contains that function? Looks like this is SDS, in which case you'd find hnbucket code in hashtab.c, and other required functions...

I'm very sorry, I'm afraid that I mis-typed! :eek: It should read: g++ -g -O2 -fPIC -o crl_idle_verify \ crl_idle_verify.o -L../../lib -lcoral \ -lhashtab -lz -lpcap Try that and see what you get. And don't worry, we'll figure this out :D

Looks like you're trying to link C++ code with gcc instead of g++.. Try using g++ for the linking stage instead and see if that helps: gcc -g -O2 -fPIC -o crl_idle_verify \ crl_idle_verify.o -L../../lib -lcoral \ -lhashtab -lz -lpcap

I don't know if this is what you're seeing, but there's an auto reboot which can be enabled which reboots if (and only if, assuming I understand this correctly) there's a system freeze or other problem that prevents the system running normally. Take a look at Chapter 3 of this PDF file