|
This thread is locked; no one can reply to it. |
1
2
|
Allegro 4.4 on Snow Leopard |
Felix-The-Ghost
Member #9,729
April 2008
|
OnlineCop
Member #7,919
October 2006
|
Mine would always fail on "make install" if the directories didn't exist first. Of course, I always compile from the Terminal instead of XCode, so I don't know how to check for "oops: couldn't install in that location..." I have to manually "mkdir /usr/local/", "mkdir /usr/local/lib/", etc. Then when I run "sudo make install" (/usr has to have admin privileges to write into), things work.
|
Felix-The-Ghost
Member #9,729
April 2008
|
But I mean isn't it too late now that I've closed the Terminal and restarted, etc? Would a manually copy/paste be fine (Are they all in one directory) Felix-The-Ghost said:
libaldat.a
to '/Developer/usr/lib' |
Evert
Member #794
November 2000
|
Felix-The-Ghost said: But I mean isn't it too late now that I've closed the Terminal and restarted, etc? Would a manually copy/paste be fine (Are they all in one directory) Don't ask, just try it. The worst that can happen is that it doesn't work. And no, it doesn't matter if you closed the terminal first (you're not setting any environment variables so how could it?) or copy the files manually.
|
Felix-The-Ghost
Member #9,729
April 2008
|
sudo didn't work. I couldn't make the usr/local etc... |
Evert
Member #794
November 2000
|
Felix-The-Ghost said: sudo didn't work. I couldn't make the usr/local etc...
So try a couple. Really, there's only 2 passwords it could be, yours or root (and that's assuming you enabled the root account, which I guess you probably haven't). Quote: I think there's a whole set in 'Developer\usr' though -- not sure if it's the same. Of course it isn't. /Developer is a different directory. Quote: and was it 'usr' or the name of the user the type in the Terminal? usr |
Felix-The-Ghost
Member #9,729
April 2008
|
I did not mean to imply we did not try. I meant to imply 'We tried, but it didn't accept any of our passwords' I can get to usr in Firefox by typing it in but not sure how/if I can open it in finder so I can make a new folder myself. Quote:
Last login: Wed Feb 24 10:44:00 on ttys000 WARNING: Improper use of the sudo command could lead to data loss To proceed, enter your password, or type Ctrl-C to abort. Password: WARNING: Improper use of the sudo command could lead to data loss To proceed, enter your password, or type Ctrl-C to abort. Password:
|
Arthur Kalliokoski
Second in Command
February 2005
|
Felix-The-Ghost said: We didn't know whose password to use for sudo. Is there a file called /etc/sudoers ? Can you view it? If it's there and you can't view it, maybe you could boot a live CD to view it. Maybe also try 'su' command. They all watch too much MSNBC... they get ideas. |
Felix-The-Ghost
Member #9,729
April 2008
|
Arthur Kalliokoski
Second in Command
February 2005
|
Does this web page help? They all watch too much MSNBC... they get ideas. |
Felix-The-Ghost
Member #9,729
April 2008
|
Evert
Member #794
November 2000
|
Felix-The-Ghost said: I can get to usr in Firefox by typing it in but not sure how/if I can open it in finder so I can make a new folder myself. Open the hard drive in the "Devices" category in the side bar of the finder window. That takes you to the root directory. Alternatively hit command-up a couple of times to go up in the directory structure. Quote: sstutzman is not in the sudoers file. This incident will be reported. That's the real problem you need to fix. I'm guessing it's /private/etc/sudoers. |
Felix-The-Ghost
Member #9,729
April 2008
|
Evert
Member #794
November 2000
|
Felix-The-Ghost said: That's this 'root' directory...?
The root directory is /, just as it is on other UNIX systems (actually, just as it is on Windows except there it's called \ instead). Quote: There's no usr, private, or etc, though. Searching reveals nothing.
What happens if you run "locate sudoers"? In terms of users/root account setup, I know you say that you enabled the root account. Are you sure? Is this your machine? Someone else's? Is it new, old? Did you change any of the system settings? Quote: There is a 'Users' with my user as one in the list. No, /Users is the OS X equivalent of /home. Not what you're looking for. |
Felix-The-Ghost
Member #9,729
April 2008
|
This is the school's computer. So is the Linux. It's probably best to just assume I have no idea of what I am doing. Locate says it needs to build a database that will take some time. Searching for 'etc' gets only 'Etched Double Line' sudo would work if I knew what password it wanted. |
Evert
Member #794
November 2000
|
Felix-The-Ghost said: This is the school's computer. So is the Linux. Aha ok, so you don't actually have administrator permissions on the machine then? That changes things a bit. You can install Allegro locally on your account rather than in a system-wide location. When you run ccmake (or the GUI-based alternative), look for CMAKE_INSTALL_PREFIX, which should be set to /usr/local. Change it to /Users/<your username> instead, then reconfigure and run "make install" again. Quote: Searching for 'etc' gets only 'Etched Double Line' Nope, has nothing to do with each other. /usr is a directory, so is /etc. You can see if it's there by looking at the contents of the root directory, either in the Finder or in the Terminal ("ls /"). If it's not there, it's not there. Quote: sudo would work if I knew what password it wanted. It wants yours, but the problem is that you're not in the sudoers file, meaning you're not allowed to sudo anything. That has nothing to do with what password it wants. |
OnlineCop
Member #7,919
October 2006
|
When Finder is open, type Command-Shift-G (letter 'G'). It opens this: {"name":"600592","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/3\/d\/3d4eb5d01fe03b7040287fe53bbb9879.png","w":433,"h":135,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/3\/d\/3d4eb5d01fe03b7040287fe53bbb9879"} As you can see, I've already typed in the path to go to. Then hit Go and it opens Finder in that directory. When you install new software on your machine, your Mac usually prompts you to put in a password. That's usually the same password you'd use for the sudo command. /usr/ is different from /Users/, and is where allegro likes to store its stuff. ./configure --help said: By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc. You can specify an installation prefix other than `/usr/local' using `--prefix', for instance `--prefix=$HOME'. This may be what you'd want to do if you don't have a password for sudo. When the Mac you (or your friend) is using was initially installed, do you remember setting some sort of "master admin" username and/or password? EDIT: beaten
|
Felix-The-Ghost
Member #9,729
April 2008
|
OnlineCop: That was indeed very helpful (I didn't know how to typ in where to go, now I see the 'Go' menu... ' However, I guess I still need privileges to make a new folder there. I'll install to my user I guess. And I'll probably use Xcode if I can't figure out Code::Blocks (I need to configure global variables and linker settings/linked libraries) Edit: Quote:
D60-MAC-07:~ sstutzman$ make install
|
Evert
Member #794
November 2000
|
Felix-The-Ghost said: I configured it to Users/me and generated but now what?
Run make from within the directory where it produced the Makefile. |
Felix-The-Ghost
Member #9,729
April 2008
|
How do I do that in ccmake? I got this is cmake: Quote:
D60-MAC-07:allegro-4.4 2 sstutzman$ cmake /Users/sstutzman/Desktop/allegro-4.4\ 2 -G "Unix Makefiles" The src is in that folder on my Desktop. What are these build files? Makefiles? There's a number of them in there...what name would this one have? ------------------------------------------------- I made a xcode project with Cmake... |
Evert
Member #794
November 2000
|
Felix-The-Ghost said: what name would this one have? Makefile. |
OnlineCop
Member #7,919
October 2006
|
Let me see if I understand correctly. You downloaded the .tar.gz sources and put them on your desktop: /Users/--you--/Desktop That should have started compiling, along with some sort of progress of the files. They should have compiled everything under the Build/ directory you had created; they won't install anything. Did it get that far?
|
Felix-The-Ghost
Member #9,729
April 2008
|
Pretty much -- except I tried the .zip version (Don't know why it'd mess up) When I tried the Cmake program I made an Xcode project with tons of errors and warnings. I don't remember ccmake terminal having that many and/or failing. I'll have to try again tomorrow. |
OnlineCop
Member #7,919
October 2006
|
I thought the only difference between the .zip and the .tar.gz files were the line endings, so the actual files should be nearly identical. The 'cmake' and 'ccmake' are the same underlying program; 'ccmake' is just the graphical interface for the same thing. I like to compile my programs all from the Terminal. So instead of creating an XCode project and makefile, I just make it for a normal Unix build, then run "make" from the console and see if it compiles. If it does, re-run 'cmake' with the flags to make it an XCode project/makefile, and see if the same errors occur. Also, if everything compiles, but it won't let you 'make install', you're basically doing everything correctly except that you need to specify that you don't want to try to install it in the sudo-protected /usr/local/ directory: have it point to somewhere on your home directory (usually ~/ or ~/Desktop/ or some-such). EDIT: Still trying to get this to compile for Felix. He got the sources from Sourceforge, extracted them to his desktop: ~/Desktop/allegro-4.4/. He opened Terminal, cd ~/Desktop/allegro-4.4/, then ran "mkdir Build/", "cd Build/", then "ccmake ..". He toggled to Advanced mode, then changed CMAKE_INSTALL_PREFIX from /usr/local to ~/usr/local (tilde at the front). He also set WANT_FRAMEWORKS from NO to YES. He also defined the following variables: export CPLUS_INCLUDE_PATH=~/usr/local/include:$CPLUS_INCLUDE_PATH export C_INCLUDE_PATH=~/usr/local/include:$C_INCLUDE_PATH export PATH=$PATH:~/usr/local/bin export LD_LIBRARY_PATH=~/usr/local/lib:$LD_LIBRARY_PATH He compiled allegro and ran make install. When that compiled and started working, he tried to compile his game. I provided a Makefile so he didn't have to recompile all the time, and got this compile error: $ make g++ -o "./bin/test" -W -Wall -g3 -ggdb3 -O0 -pg ./obj/Ball.o ./obj/Paddle.o ./obj/Pong.o ./obj/Powerup.o `allegro-config --libs` ld: warning: in /Users/sstutzman/usr/local/lib/liballeg-main.a, file is not of required architecture ld: warning: in /Users/sstutzman/usr/local/lib/liballeg.dylib, file is not of required architecture I had him try to add "-m32" to the end of his linking command, and it got rid of that error, but then gave him this: $ make g++ -o "./bin/test" -W -Wall -g3 -ggdb3 -O0 -pg -m32 ./obj/Ball.o ./obj/Paddle.o ./obj/Pong.o ./obj/Powerup.o `allegro-config --libs` ld: warning: in ./obj/Ball.o, file is not of required architecture ld: warning: in ./obj/Paddle.o, file is not of required architecture ld: warning: in ./obj/Pong.o, file is not of required architecture ld: warning: in ./obj/Powerup.o, file is not of required architecture We tried changing from "-m32" to "-m64", but that just gave the original error (since allegro wasn't compiled as a 64-bit). He's running Snow Leopard (10.6). I don't get this error on Leopard (10.5), so I'm not sure what's going wrong.
|
Felix-The-Ghost
Member #9,729
April 2008
|
|
1
2
|