PlaneShift
Development => Development Deliberation => gcc => Topic started by: Gergon on December 26, 2007, 11:28:47 pm
-
I downloaded it with the SVN commands.
It compiled fine with no errors, but it put all the files that had been made in my home directory. (not the Development one)
Is it soposed to do that? If not how can fix this?
EDIT:::
I moved the compilied files to the cs folder, and it works, but when I tried to configure CEL the terminal says this:
checking for cs-config-1.1... no
checking for cs-config-1.2... ./cs-config-1.2
checking if Crystal Space version >= 1.1... yes (version 1.2)
checking if Crystal Space SDK is usable... no
configure: error:
*** Crystal Space could not be found or was unusable. The latest version is
*** always available from http://www.crystalspace3d.org/
*** Also, be sure that you have either installed Crystal Space or set the
*** CRYSTAL environment variable properly.I did use the command to export the crystal space directory before this.
Thanks,
Gergon
-
echo $CRYSTAL
What does that command produce?
-
It doesn't do anything.
-
We should add the CRYSTAL environment variable to the .bashrc file so applications outside the Crystal Space tree know where to find the .so's.
export CRYSTAL=/home/user/development/cs
looks like you missed part of this step
-
I did, I guess I was hurrying and didn't read it and used it as a command. ;D
I have added the working directory's, but it still does the same thing, CS is unusable.
I know the directory's are set right because when I type in export $CRYSTAL, it comes up with the right directory.
What could be the problem? ???
In the mean time, ill recompile it and see if it helps. ;)
-
It works now, thanks for the help, but CEL is not detecting Jam, I'll redownload it.
But I still can't figure out why it puts all the compiled files in my home directory.
Thanks for your help!
Gergon
-
you mean all the files you downloaded are in one folder?
dont do that download the files again but this time follow the build guide putting cal3d in a cal3d folder cs in a cs folder cel in a cel folder and ps in a planeshift folder. then start the build process over again
-
Oh, no, there in separate folders, see my directory is /home/cody/Development/(cs, cel, cal3d, or planeshift).
When I compile something like cs, all the built files get put in /home/cody.
Also, when I go to build CEL the terminal says this:
Jamfile: No such file or directory
don't know how to make libs
don't know how to make plugins
don't know how to make cel-config
...found 4 target(s)...
...can't find 3 target(s)...
I do have Jam installed, what could be the problem there?
-
did you configure first? [are you reading and following word for word the build guide?]
-
Yes, I configured it first, but it put all the files that it configured in the /home directory, I moved them back to the Development directory in the cel folder.
-
:sweatdrop: Well, it started to compile, I configured it again, instead of using the command on the compiling guide I typed in jam right after the configuring was finished.
-
Thanks for the help everyone. :thumbup:
-
I'm having problems compiling CS now too. I am using SuSe 10.1 and the gcc is 4.1.0. I'm getting:
C++ ./out/linuxx86/optimize/plugins/sndsys/renderer/software/source.o
plugins/sndsys/renderer/software/source.cpp: In member function ‘void SndSysSourceSoftware3D::SetupFilters()’:
plugins/sndsys/renderer/software/source.cpp:560: internal compiler error: in merge_alias_info, at tree-ssa-copy.c:235
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.suse.de/feedback> for instructions.
Is it too obvious to ask if 4.1.0 is the problem? I'm seeing a few people say they can do it with 4.1.1, or has anyone seen a similar problem before with this module?
-
After a quick google, it seems you will need to update your compiler, here (http://trac.sagemath.org/sage_trac/ticket/908) for example.
-
Thanks. Yeah, I was being lazy. Was going to check CS's page today and see what might be happening, but I was pretty positive it would end up being my version. I love Linux, but man, they do break things way too much. Sometimes just get tired of chasing all their bugs.
-
Alright, scratch gcc 4.1.0 from the list of supported compilers for this build. Spent the day upgrading my system (thanks to a down server) to SuSe 10.3, gcc 4.2.1, and all of it compiled with no modifications needed. Seems the mob issue is close to settled. I don't quite have a playable system yet, but just have to do the configuration steps now. If I see an opportunity to help out, I will. I'm sure you're thrilled. ;)