To do this you will need to install Xcode from App Store and then its command line tools from an option in Xcode as you need a development environment.
It might be easier to use a package manager like Macports or Homebrew after that to install apache and mod_wsgi. the writers of the package will have sorted out any issues.
I will explain the commands in the line after each one
curl -o mod_wsgi.tgz http://modwsgi.googlecode.com/files/mod_wsgi-2.5.tar.gz
Get the source code from the given server. curl is a program that downloads via http. You could just enter the URL in your browser and download the file. The curl command puts the mod_wsgi.tgz in your current directory.
tar -xzf mod_wsgi.tgz
Untar the file - ie get all the individual files out of the package and put them in the correct subdirectories. If you had downloaded in your browser the default action would have down this unpack, or select this file in Finder and double click to extract.
cd mod_wsgi-2.5
Change directory into the top level of the source code. If you had used the browser in the first two steps then cd ~/Downloads/mod_wsgi-2.5
./configure
The source code can be built for many versions of Unix, Linux and possible other operating systems. configure is a shell script that calls on certain programs in Xcode to generate the correct source code files so that this setup will build on OSX. The ./ is required as your current directory is not on your path.
make
Make an executable and support files out of the source code. This will all be in or beneath your current directory. make is a program that does things based on a set of rules held in makefiles.
sudo make install
This puts the executables in a directory that can be used by apache. make install
uses the make program as above but with a command install to do something different (actually if you had not done make before it will also do the build as in the command above as that is defined as a dependency on the makefile but don't do this because of the sudo) sudo is a command that makes the rest of the line run as the root user, this is needed as you should not have permission to write to the directories the executables should end up in, this you need a special command to get that permission. Note that your user needs to be set up to use sudo, if you are an Administrator then that will be sufficient.
This should give you enough pointers to help you read up on anything that I have started to explain.
I think I have a solution to this problem.
After upgrading to Mavericks my saved presets for a Brother Laser printer still worked fine, but for an Epson Inkjet they would load, like you describe. I thought it was the printer or OS conflict as the Epson was attached by USB to a machine running OS X 10.6 and I was sharing to the Mavericks machine. However I got a new wireless Epson Inkjet and the problem persisted.
Here's what I did to fix it.
- Log in to an administrator account. Make a new one if you need to and give it full privileges.
- Open an app that lets you print, Safari say.
- Type Cmd-P and select the problem printer, set your options and save the preset.
- Click Print, just to make sure it's working.
- Type Cmd-P and check that your settings have stuck, if they haven't try again with another user account, if they have carry on.
- Quit the App you used above.
- In the Finder Opt-Click the Go menu and select Library.
- Navigate to Preferences.
- Copy the file com.apple.print.custompresets.forprinter.[yourprintername].plist to the Desktop.
- Change the owner of the file to the account that is having problems (chown [username] com.apple.print.custompresets.forprinter.[yourprintername].plist) if this fails precede the command with sudo.
- Copy the file from the Desktop to the Drop Box of the user having problems (/Users/[username]/Public/Drop Box, or you could email it to yourself or use Dropbox (as in the cloud service).
- Log out of the admin account and back in to your usual one.
- Repeat step 7 and 8 above
- Delete the com.apple.print.custompresets.forprinter.[yourprintername].plist
- Copy your new com.apple.print.custompresets.forprinter.[yourprintername].plist from your Drop Box folder.
- Select the new file and type Cmd-I. Scroll down to the bottom of the Get Info window and check that your current username is the one listed with Read/Write access.
- Log out
- Log back in
- Try to print something. Hopefully you will now have a working preset.
Hope this is useful
Best Answer
Do you have a netgear router?
Look here and search for “printer”. It looks like it could be something to do with vulnerability scanning in your router.
Suggestions are: