Re: trouble with libgomp/.deps directory building gcc 4.7.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 19 December 2012 00:36, Tim Bird wrote:
> On 12/18/2012 12:12 PM, Tim Bird wrote:
>> I am trying to build gcc-4.7.2 (September tarball release) on Ubuntu 12.04.
>> Some ways into the build I get the following error processing the libgomp directory:
>>
>> make[3]: Entering directory `/a/home/tbird/work/auto-reduce/lto-work/obj-gcc/x86_64-unknown-linux-gnu/libgomp'
>> Makefile:456: .deps/affinity.Plo: No such file or directory
> ...
>> Makefile:480: .deps/work.Plo: No such file or directory
>> make[3]: *** No rule to make target `.deps/work.Plo'.  Stop.
>> make[3]: Leaving directory `/a/home/tbird/work/auto-reduce/lto-work/obj-gcc/x86_64-unknown-linux-gnu/libgomp'
>> make[2]: *** [all-stage1-target-libgomp] Error 2
>> make[2]: Leaving directory `/a/home/tbird/work/auto-reduce/lto-work/obj-gcc'
>> make[1]: *** [stage1-bubble] Error 2
>> make[1]: Leaving directory `/a/home/tbird/work/auto-reduce/lto-work/obj-gcc'
>> make: *** [all] Error 2
>
> FYI -  I deleted both my build directory (obj-gcc)

I was going to suggest that.  For GCC 'make clean' isn't as effective
as removing everything, it doesn't remove Makefiles for starters.

> and the source directory

Unnecessary, that's the major benefit of the build directory being
separate from the source directory, the source directory is never
touched (and could even be read-only).

(However if you have previously built in the source directory then it
is worth deleting ti and starting again, but as long as you always
build in a separate build dir the sources will stay pristine.)


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux