| Summary: | xfree 4.2.1-r2 fails with No rule to make target `clean'. | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Sachin Kamboj <skamboj> |
| Component: | Unclassified | Assignee: | Martin Schlemmer (RETIRED) <azarah> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | David.Huff, martin, mbaptist, mholzer |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Sachin Kamboj
2003-03-08 13:49:07 UTC
I've had the exact same results my writeup is here: http://forums.gentoo.org/viewtopic.php?t=40464 This does not happen if one comments out the -j7 (or whatever -j) option in /etc/make.conf. *** Bug 16693 has been marked as a duplicate of this bug. *** as an apendix to the same prob i have posted in BUG-ID 16693: I've recompiled (emerged :-) ) x11-base/xfree-4.2.1-r2 with Portage 2.0.47-r8 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r2) with an uncommented #MAKE_OPTS="-j7" in etc/make.conf. For me it worked fine, Thx ! Eventually I was able to emerge xfree-4.3.0: ACCEPT_KEYWORDS="~x86" emerge x11-base/xfree/xfree-4.3.0.ebuild Of course it unmasked and compiled a couple of other modules but it worked all with the same setting so it must be something in the 4.2.1-r2 build process. Gnome is a little unstable but works well enough until other packages sync up with xfree. This also seems related to gcc 3.2.1, as removing -j7 didn't work for me until I emerged gcc 3.2.2 I got the same problem in XFree 4.3.0. I couldn't get it to work irrespective of the MAKEOPTS and CFLAGS set. I finally ended up downloading the binary from xfree86.org and installing it manually. I also "injected" xfree into the world database and then went on to install kde and the rest. Its working perfectly fine and stable so far. Hello, According to the changelog, ths problem existed in xfree-4.3 too, but was fixed by unsetting make_opts in the ebuild. If make_opts is defined in /etc/make.conf, the xfree build will die this way. As far as I can tell, make_opts should not be set in /etc/make.conf - but be changed to makeopts (without the underscore). Strangely, on my completely new system, make_opts was set at the very beginning at the make.conf, while makeopts was commented out further down, where one would usually find it. In the original case I ran it with makeopts (without the underscore) - see the emerge info output in the original post. Anway I tried commenting it out all-together but it still failed. It might be a problem with gcc - downloading the original source from the xfree86.org and compiling did not work either!! Ok, I think I've narrowed this down. Several different things come into play: 1.) I built a box using the the default make?opts settings two weeks ago from rc_2 stage 1. But that was on gcc-3.2.1. Everything worked fine. 2.) The next time I built a machine from rc3_stage 3, then "emerged -u system" and therefore gcc was updated before I tried to install xfree. That got me to gcc-3.2.2. But with the new release the developers pended the make_opts="-j7" to the end of the download address in the make.conf file and *also* left the makeopts="-j2" down towards the bottom of the file. 3.) Since I have a small MOSIX puffin farm I was able to try the various combinations. Well, at least for me if I want to keep gcc-3.2.2, I needed to comment out both the make?opts statements and it worked! Now I going to "emerge gnome" again to get it all in sync with xfree since I had already built up the system on xfree-4.3. In Summary: It was the combinations of xfree the make?opts variable and the gcc versioning. Easy huh? azarah: this is really a problem since user are not able to emerge xfree i've just installed with rc3 livecd and got the same error Unset MAKE_OPTS in 4.2.1-r2 as well. |
