09-17-2011, 11:03 AM
Hum I think the warning because I do not use the variable but only it status (which is not the best but that not so important )
PCSX2 for Fedora
|
09-17-2011, 11:03 AM
Hum I think the warning because I do not use the variable but only it status (which is not the best but that not so important )
09-17-2011, 03:39 PM
I'm experimenting with the shell script to open pcsx2 with LD_PRELOAD options.
I noticed you had modified the launch_pcsx2_linux.sh script to include an LD_PRELOAD option. Unfortunately this gets kicked out with an error without loading the gsdx plugin on startup: Code: Loading plugins... Calling the LD_PRELOAD option directly through a shell script works, but the console kicks out an error each time when the gsdx plugin is called: Code: #!/bin/sh -e I don't suppose this matters much in the big scheme of things, as I'll compile the target pcsx2 binary to a fixed place in fedora, so won't need a complex script to launch it, but in the interests of everything eventually being clean and tidy, I wonder if it is possible to prevent pcsx2 having an error on detecting the sdl library?
Hmmm. Think I must have broken the build with my patch. When I try to compile the rpm, the build stops:
The build is started with: Code: cmake CMakeLists.txt -DPACKAGE_MODE=TRUE -DCMAKE_INSTALL_PREFIX="/usr" -DPLUGIN_DIR=%{_libdir}/%{name} -DGAMEINDEX_DIR=%{_datadir}/%{name} -DFORCE_INTERNAL_SOUNDTOUCH=FALSE -DFORCE_INTERNAL_SDL=TRUE -DSHARED_SDL=libpcsx2_SDL -DCMAKE_BUILD_TYPE=Release Code: [ 23%] Built target Utilities Patch code is: Code: --- pcsx2-4918/pcsx2/gui/Dialogs/FirstTimeWizard.cpp Is there any reason the patch should affect things like this...? Interestingly, when I patch and build from the comand line I don't get this error - however the pcsx2 binary isn't created. However I think this is to do with build type only installing into a protected directory (and rpm build profile has no root privilege for security): Code: $ make install Not really sure why the rpmbuild is crashing out during the padNull operation... I'll try building the rpm without the patch to confirm that it's the problem... EDIT: Not the patch afterall. Same error. Just unhappy with the build for some reason...
09-19-2011, 07:50 PM
Do you use the -j option to compile severals files in parallel? In this case the log file will not stop in the latest bad step but will continue some on going work. However if PadNull is an issue just remove the plugin directory, it is not critical
IMHO, RPM root is chrooted so it can access /var/games, it you build it from command line, /var is your real one hence the security permission issue.
09-19-2011, 08:36 PM
Quote:Do you use the -j option to compile severals files in parallel? as "cmake foobar -j "...? No... I have the output of CMakeFiles/CMakeError.log I don't know if it's relevant: Code: Determining if the function pthread_create exists in the pthreads failed with the following output: Quote:However if PadNull is an issue just remove the plugin directory, it is not critical I don't think it's the issue but can I specify to build without PadNull to test this out?
Well it was actually make -j 4
Anyway, you can select which plugins is built in the file cmake/SelectPcsx2Plugins.cmake. Just set(PadNull FALSE) Hum the ouptut is interesting, you have an issue with a library Quote:/usr/bin/ld: cannot find -lpthreadsBy the way how do you generate the log ? Edit: However I think this error is expected because linux have pthread and pthreads
09-19-2011, 09:19 PM
The log generated itself somehow I was looking for some error log for clues. I'll try building again with PadNull set to false.
09-19-2011, 10:06 PM
Ok. I only have this one CMakeFiles/CMakeOutput.log. Probably because I do not have any error Could you attach this one too (use gzip).
I notice that you have several -march gcc parameter. Maybe there is some unlikely conflict.
09-20-2011, 07:29 AM
Um - maybe you could help me with the patch to stop PadNull being built too I don't know what the second number (164, n) is for in the patching code (thought I did... but clearly was decieving myself)
Code: --- pcsx2-4918/cmake/SelectPcsx2Plugins.cmake The CMakeOutputLog is attached.
Patch seem correct, otherwise move the Padnull directory outside of the tree. The second number is the column
Strangely I do not the the pthread stuff at the end of my log file. Could you do a grep into cmake configuration script (*.cmake file). On debian there are installed into /usr/share/cmake-2.8 Code: grep -irw pthreads /usr/share/cmake-2.8/ Edit: could you post also cmake autodetection information too. |
« Next Oldest | Next Newest »
|