Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
Write an article for LinuxForums Today! Win Great Prizes!
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-util/cmake-2.6.3-r1/work/cmake-2.6.3 ...
>>> Working in BUILD_DIR: "/var/tmp/portage/dev-util/cmake-2.6.3-r1/work/cmake-2.6.3"
make -j2
Scanning dependencies of target cmsysTestDynload
Scanning dependencies of target cmsys
[ 1%] Building C object Source/kwsys/CMakeFiles/cmsysTestDynload.dir/testDynload.o
i686-pc-linux-gnu-gcc: DEFINES: No such file or directory
[ 1%] Building C object Source/kwsys/CMakeFiles/cmsys.dir/ProcessUNIX.o
make[2]: *** [Source/kwsys/CMakeFiles/cmsysTestDynload.dir/testDynload.o] Error 1
make[1]: *** [Source/kwsys/CMakeFiles/cmsysTestDynload.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
i686-pc-linux-gnu-gcc: DEFINES: No such file or directory
[ 1%] Building C object Source/kwsys/CMakeFiles/cmsys.dir/Base64.o
i686-pc-linux-gnu-gcc: DEFINES: No such file or directory
make[2]: *** [Source/kwsys/CMakeFiles/cmsys.dir/Base64.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [Source/kwsys/CMakeFiles/cmsys.dir/ProcessUNIX.o] Error 1
make[1]: *** [Source/kwsys/CMakeFiles/cmsys.dir/all] Error 2
make: *** [all] Error 2
*
I am not sure what causes these bugs, I've seen a couple of them in bugzilla but I know very little about cmake so I don't know how to fix those. You could check these two, which seem to be very similar:
Thanks i92guboj,
I was just looking on the bug report site, I found a few similar ones too. Currently I got emerge to continue by using --skipfirst, hopefully It'll pull in an extra package that will help cmake compile. If I can't get this to work eventually, I will file a bug report.
__________________
I do not respond to private messages asking for help.
Please keep it on the forums only.
I saw this for the first time just the other day, can you use that just as you would --skipfirst?
By default emerge will stop when a package fails to merge for some reason. In this case, --keep-going will instruct emerge to continue with the next package instead while --skipfirst will just skip the first package in the list.
I suggested that because it could take a bit to get this fixed. In the while you can just add --keep-going, so you don't have to care about cmake each time you update your system. Another option would be to mask the problematic version of cmake, but then you might not notice when it's fixed until you remember to unmask it.
You could continue using --skipfirst as well, nothing bad about that. Just that each time you update you will have to do it in two batches.
Thanks man, this would have come in handy so many times in the past. I actually re-installed about 3 months ago just because I couldn't get emerge to finish anything. This is going to make things alot easier.
__________________
I do not respond to private messages asking for help.
Please keep it on the forums only.
Open Source Security Myths Dispelled Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization subscribe
InformationWeek InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology. subscribe
Gentoo Linux Help For help and discussion related to Gentoo Linux
Submit Your Article
Latest Articles
Editor's Choice
Article Categories
Join Linux Forums Today
Win Great Prizes
Linear Mode
