Louis_marie_c Posted December 30, 2011 Report Share Posted December 30, 2011 (edited) g++ -fvisibility=hidden -W -Wall -Wno-unused-parameter -Wno-unused-function -fPIC -fno-strict-aliasing -O0 -g -D_DEBUG -DRETAIL -IFCollada `pkg-config libxml-2.0 --cflags` -MD -MF output/debug/FCollada/FUtils/FUXmlDocument.d -c FCollada/FUtils/FUXmlDocument.cpp -o output/debug/FCollada/FUtils/FUXmlDocument.oFCollada/FUtils/FUXmlParser.cppg++ -fvisibility=hidden -W -Wall -Wno-unused-parameter -Wno-unused-function -fPIC -fno-strict-aliasing -O0 -g -D_DEBUG -DRETAIL -IFCollada `pkg-config libxml-2.0 --cflags` -MD -MF output/debug/FCollada/FUtils/FUXmlParser.d -c FCollada/FUtils/FUXmlParser.cpp -o output/debug/FCollada/FUtils/FUXmlParser.omake: *** No rule to make target `output/debug/FColladaPlugins/FArchiveXML/FArchiveXML.o', needed by `output/libFColladaSD.a'. Stop.make: *** Waiting for unfinished jobs....FCollada/FUtils/FUXmlWriter.cppg++ -fvisibility=hidden -W -Wall -Wno-unused-parameter -Wno-unused-function -fPIC -fno-strict-aliasing -O0 -g -D_DEBUG -DRETAIL -IFCollada `pkg-config libxml-2.0 --cflags` -MD -MF output/debug/FCollada/FUtils/FUXmlWriter.d -c FCollada/FUtils/FUXmlWriter.cpp -o output/debug/FCollada/FUtils/FUXmlWriter.oERROR: FCollada build failedI tried to compile 0AD on my Mac 3 times but everytime i've this error and i don't know how i can fix that. Anyone can help me ? ThanksI put all the line in the attachment file to help you(Excuse me for the bad english i'm french )FColladaBuildFailed.txt Edited December 30, 2011 by Louis_marie_c Quote Link to comment Share on other sites More sharing options...
historic_bruno Posted December 30, 2011 Report Share Posted December 30, 2011 Have you tried ./clean-workspaces.sh? Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted December 30, 2011 Author Report Share Posted December 30, 2011 Have you tried ./clean-workspaces.sh?Thanks for the reply i tried and i've this /clean-workspaces.sh Cleaning bundled third-party dependencies.../Users/me/0ad/build/workspaces/clean-workspaces.sh: line 13: cd: ../../libraries/spidermonkey: No such file or directory/Users/me/0ad/build/workspaces/clean-workspaces.sh: line 14: cd: ../../libraries/spidermonkey: No such file or directory/Users/me/0ad/build/workspaces/clean-workspaces.sh: line 15: cd: ../../libraries/nvtt/src: No such file or directoryCleaning Premake4Cleaning build output...Done. Try running update-workspaces.sh again now. Quote Link to comment Share on other sites More sharing options...
Yves Posted December 30, 2011 Report Share Posted December 30, 2011 /Users/me/0ad/build/workspaces/clean-workspaces.sh: line 13: cd: ../../libraries/spidermonkey: No such file or directory/Users/me/0ad/build/workspaces/clean-workspaces.sh: line 14: cd: ../../libraries/spidermonkey: No such file or directoryAre you sure the sources are complete? Did you get them from subversion? Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted December 30, 2011 Author Report Share Posted December 30, 2011 Are you sure the sources are complete? Did you get them from subversion?I get them with this command line (svn co http://svn.wildfiregames.com/public/ps/trunk/ 0ad) and tried to compile and i've this result Quote Link to comment Share on other sites More sharing options...
Yves Posted December 30, 2011 Report Share Posted December 30, 2011 try running svn upin /Users/me/0ad Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted December 30, 2011 Author Report Share Posted December 30, 2011 Thank you for the time is now to restore files I'll let you know Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted December 30, 2011 Author Report Share Posted December 30, 2011 After svn up and clean-workspaces the compilation failed again with the same error ERROR: FCollada build failedAnd i don't know why Quote Link to comment Share on other sites More sharing options...
Yves Posted December 30, 2011 Report Share Posted December 30, 2011 Hmm I don't know exactly what the problem is and I'm still trying to find it out... but you could run clean-workspaces.sh again and thenupdate-workspaces.sh -j1 in the meantime and post the output.This could probably also solve the problem. Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted December 31, 2011 Author Report Share Posted December 31, 2011 Hmm I don't know exactly what the problem is and I'm still trying to find it out... but you could run clean-workspaces.sh again and thenupdate-workspaces.sh -j1 in the meantime and post the output.This could probably also solve the problem.I tried your solution but i've the same resultthis is the last few lines g++ -fvisibility=hidden -W -Wall -Wno-unused-parameter -Wno-unused-function -fPIC -fno-strict-aliasing -O0 -g -D_DEBUG -DRETAIL -IFCollada `pkg-config libxml-2.0 --cflags` -MD -MF output/debug/FCollada/FUtils/FUUri.d -c FCollada/FUtils/FUUri.cpp -o output/debug/FCollada/FUtils/FUUri.oFCollada/FUtils/FUXmlDocument.cppg++ -fvisibility=hidden -W -Wall -Wno-unused-parameter -Wno-unused-function -fPIC -fno-strict-aliasing -O0 -g -D_DEBUG -DRETAIL -IFCollada `pkg-config libxml-2.0 --cflags` -MD -MF output/debug/FCollada/FUtils/FUXmlDocument.d -c FCollada/FUtils/FUXmlDocument.cpp -o output/debug/FCollada/FUtils/FUXmlDocument.oFCollada/FUtils/FUXmlParser.cppg++ -fvisibility=hidden -W -Wall -Wno-unused-parameter -Wno-unused-function -fPIC -fno-strict-aliasing -O0 -g -D_DEBUG -DRETAIL -IFCollada `pkg-config libxml-2.0 --cflags` -MD -MF output/debug/FCollada/FUtils/FUXmlParser.d -c FCollada/FUtils/FUXmlParser.cpp -o output/debug/FCollada/FUtils/FUXmlParser.oFCollada/FUtils/FUXmlWriter.cppg++ -fvisibility=hidden -W -Wall -Wno-unused-parameter -Wno-unused-function -fPIC -fno-strict-aliasing -O0 -g -D_DEBUG -DRETAIL -IFCollada `pkg-config libxml-2.0 --cflags` -MD -MF output/debug/FCollada/FUtils/FUXmlWriter.d -c FCollada/FUtils/FUXmlWriter.cpp -o output/debug/FCollada/FUtils/FUXmlWriter.omake: *** No rule to make target `output/debug/FColladaPlugins/FArchiveXML/FArchiveXML.o', needed by `output/libFColladaSD.a'. Stop.ERROR: FCollada build failed Quote Link to comment Share on other sites More sharing options...
Yves Posted December 31, 2011 Report Share Posted December 31, 2011 Does "svn up" only return "Revision 10836." or does it still download anything?And does the file 0ad/libraries/fcollada/src/FColladaPlugins/FArchiveXML/FArchiveXML.cpp exist? Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted December 31, 2011 Author Report Share Posted December 31, 2011 (edited) Does "svn up" only return "Revision 10836." or does it still download anything?And does the file 0ad/libraries/fcollada/src/FColladaPlugins/FArchiveXML/FArchiveXML.cpp exist?Yes svn up return Revision 10836 onlyUpdating '.':À la révision 10836.yes the file exist but isn't in the right place ...it was in 0ad/libraries/fcollada/FColladaPlugins/FArchiveXML/FArchiveXML.cpp Edited December 31, 2011 by Louis_marie_c Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted December 31, 2011 Author Report Share Posted December 31, 2011 OK now the game was compiled but the app folder was empty Here is the last few lines ld: symbol(s) not found for architecture x86_64collect2: ld returned 1 exit statusmake[1]: *** [../../../binaries/system/test.app/Contents/MacOS/test] Error 1make: *** [test] Error 2ReplaceTerrain.cppSmoothElevation.cppTransformObject.cppBrushes.cppMiscState.cppObjectSettings.cppTools.cppLinking AtlasUIld: warning: ignoring file /System/Library/Frameworks//QuickTime.framework/QuickTime, file was built for unsupported file format which is not the architecture being linked (x86_64)And the complete details are in the attached fileAppBundle.txt Quote Link to comment Share on other sites More sharing options...
Yves Posted December 31, 2011 Report Share Posted December 31, 2011 ld: warning: ignoring file /Library/Frameworks//OpenAL.framework/OpenAL, file was built for unsupported file format which is not the architecture being linked (x86_64)ld: warning: ignoring file /System/Library/Frameworks//QuickTime.framework/QuickTime, file was built for unsupported file format which is not the architecture being linked Apparently it can't find those libraries in 64 bit version. That's either because there aren't any or because it doesn't look at the right place.Can you find a 64 bit version of those Frameworks on your system? Use the "file"-command to determine the architecture of libraries and objectfiles.Unfortunately I don't know the mac very well and don't have a lion-system to make any tests. Quote Link to comment Share on other sites More sharing options...
historic_bruno Posted December 31, 2011 Report Share Posted December 31, 2011 I also get the QuickTime warning but it doesn't seem to cause any problems. The OpenAL warnings are bad, what's the result of running uname -a? Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted January 2, 2012 Author Report Share Posted January 2, 2012 I also get the QuickTime warning but it doesn't seem to cause any problems. The OpenAL warnings are bad, what's the result of running uname -a?With uname -a i've this .local 11.2.0 Darwin Kernel Version 11.2.0: Tue Aug 9 20:54:00 PDT 2011; root:xnu-1699.24.8~1/RELEASE_X86_64 x86_64 Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted January 2, 2012 Author Report Share Posted January 2, 2012 (edited) I've modified a file on OpenAL Framework change ALCVoid by Void And the first error has been corrected but now i've thisld: symbol(s) not found for architecture x86_64collect2: ld returned 1 exit statusmake[1]: *** [../../../binaries/system/test.app/Contents/MacOS/test] Error 1make: *** [test] Error 2FillTerrain.cppFlattenElevation.cppPaintTerrain.cppPlaceObject.cppReplaceTerrain.cppSmoothElevation.cppTransformObject.cppBrushes.cppMiscState.cppObjectSettings.cppTools.cppLinking AtlasUIld: warning: ignoring file /System/Library/Frameworks//QuickTime.framework/QuickTime, file was built for unsupported file format which is not the architecture being linked (x86_64)And a new folder on 0ad/build/workspaces/ with all the xcodeproj files. I tried another compilation but like the last, the app is empty Edited January 2, 2012 by Louis_marie_c Quote Link to comment Share on other sites More sharing options...
Yves Posted January 3, 2012 Report Share Posted January 3, 2012 The output you posted does not contain the error messages.Could you please post the entire output? Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted January 3, 2012 Author Report Share Posted January 3, 2012 The output you posted does not contain the error messages.Could you please post the entire output?I put all the log in the file thanks for your helpLog.txt Quote Link to comment Share on other sites More sharing options...
Yves Posted January 3, 2012 Report Share Posted January 3, 2012 I put all the log in the file thanks for your helpActually the same error is still present...ld: warning: ignoring file /Library/Frameworks//OpenAL.framework/OpenAL, file was built for unsupported file format which is not the architecture being linked (x86_64) Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted January 3, 2012 Author Report Share Posted January 3, 2012 Actually the same error is still present...ld: warning: ignoring file /Library/Frameworks//OpenAL.framework/OpenAL, file was built for unsupported file format which is not the architecture being linked (x86_64)sorry I had not seen this error. I do not understand why I did, because looking at my version ofOpenAL I see this :file /System/Library/Frameworks/OpenAL.framework/OpenAL /System/Library/Frameworks/OpenAL.framework/OpenAL: Mach-O universal binary with 2 architectures/System/Library/Frameworks/OpenAL.framework/OpenAL (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64/System/Library/Frameworks/OpenAL.framework/OpenAL (for architecture i386): Mach-O dynamically linked shared library i386 Quote Link to comment Share on other sites More sharing options...
Yves Posted January 4, 2012 Report Share Posted January 4, 2012 I can spot two differences in these paths...The one in the logfile:/Library/Frameworks//OpenAL.framework/OpenALThe one you checked with "file":/System/Library/Frameworks/OpenAL.framework/OpenALThe double-slash seems strange. I've googled this path (/Library/Frameworks//OpenAL.framework/OpenAL) and found out that some other people have this error too with other software.One example: https://trac.macports.org/ticket/23222"/System/Library/Frameworks/OpenAL.framework/OpenAL" seems to be the right path. I don't know if removing the other one is a good idea or not. Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted January 4, 2012 Author Report Share Posted January 4, 2012 I can spot two differences in these paths...The one in the logfile:/Library/Frameworks//OpenAL.framework/OpenALThe one you checked with "file":/System/Library/Frameworks/OpenAL.framework/OpenALThe double-slash seems strange. I've googled this path (/Library/Frameworks//OpenAL.framework/OpenAL) and found out that some other people have this error too with other software.One example: https://trac.macports.org/ticket/23222"/System/Library/Frameworks/OpenAL.framework/OpenAL" seems to be the right path. I don't know if removing the other one is a good idea or not.Ok thanks for your help i tried this things Rename /Library/Frameworks//OpenAL.framework/OpenAL in /Library/Frameworks//OpenAL.framework/OpenAL.bak And copy/past this one /System/Library/Frameworks/OpenAL.framework/OpenAL Quote Link to comment Share on other sites More sharing options...
Yves Posted January 4, 2012 Report Share Posted January 4, 2012 Ok thanks for your help i tried this things Rename /Library/Frameworks//OpenAL.framework/OpenAL in /Library/Frameworks//OpenAL.framework/OpenAL.bak And copy/past this one /System/Library/Frameworks/OpenAL.framework/OpenAL... and did it solve the problem? Quote Link to comment Share on other sites More sharing options...
Louis_marie_c Posted January 4, 2012 Author Report Share Posted January 4, 2012 ... and did it solve the problem?is being compiled I will keep abreast Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.