Renamed ebuild of nvclock-0.8_beta2 seems to work.
Created attachment 140252 [details] nvclock-0.8_beta3.ebuild
Renaming it doesn't work for me, and the error I get is weird: /usr/bin/install -c -c nvclock /var/tmp/portage/media-video/nvclock-0.8_beta3/distdir/var/tmp/portage/media-video/nvclock-0.8_beta3/image/usr/bin/nvclock /usr/bin/install: cannot create regular file `/var/tmp/portage/media-video/nvclock-0.8_beta3/distdir/var/tmp/portage/media-video/nvclock-0.8_beta3/image/usr/bin/nvclock': No such file or directory make[1]: *** [install-app] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-video/nvclock-0.8_beta3/work/nvclock0.8b3/src' make: *** [install] Error 2 I'm running on amd64. It's clearly prepending the path twice, but I can't see why or why the OP didn't have the same problem. Any ideas?
Created attachment 140645 [details] nvclock with makefile patch fix for x86_64 arch I'm attaching an updated ebuild that works on my 64bit system. Makefile patch to follow.
Created attachment 140646 [details, diff] nvclock 64bit Makefile patch
Just like to add that the patched ebuild with the makefile patch worked fine for me on my system with an 8800GTX, beta 2 did not.
It also works for me (amd64).
Any update on this package?
Jeremy, Thanks for your ebuild and patch. I had trouble compiling it on my computer as I can't seem to find that qt patch that your ebuild calls. However, I changed the use flag to be "-qt3 -gtk" and it builds fine. I'm running an AMD64 with an 8800gts (g92) card. I use a bunch of features on nvclock and they all are working fine. What does it take to get an ebuild put in the main portage tree and not have it masked by the ~amd64 flag? p.s. If someone could point me to the qt patch, I would be more than happy to test the GUIs with this program and get back to you all.
Hello guys, The amd64 patch may work fine in amd64 systems, but it might not be the best solution since it is simply hardcoding everything in the makefile. Cheers
Created attachment 166391 [details, diff] Makefile.in patch Patch to fix Makefile.in, should work on every platform supported and be more correct than previous solutions.
Created attachment 166392 [details, diff] Fix few fails in src/gtk Missing includes and (char*)a?b:c fail.
Created attachment 166393 [details] modified ebuild with both patches and obsolete stuff removed Replaced autogen.sh with eautoreconf, ./configure with econf. Removed lib64 qt hack. Added both my patches.
Created attachment 176820 [details] Live ebuild Live ebuild to support 9XXX cards, adds smartdimmer use flag to optionally install smartdimmer binary
Created attachment 176822 [details, diff] Smartdimmer installation patch epatch for previous ebuild, enables installing smartdimmer on use flag
Created attachment 176831 [details, diff] Adds options to smoothly fade on brightness change Rewrote patch from #158685 to enable pretty fading effects in (maintained) smartdimmer from this build
Created attachment 176832 [details] Live ebuild with fade support Updated ebuild to enable previous patch via USE flag
0.8 beta 4 version bump
Created attachment 178510 [details] Version bump to 0.8_beta4 Just an ebuild for the new version beta4. The patch nvclock_acinclude_qtlibs.patch is still needed to get it going with qt.
Could you please update nvclock top beta4 in portage, as beta2 and beta3 both have a problem in the code parsing bios leading to problems with SSP on hardened?
(In reply to comment #19) > Could you please update nvclock top beta4 in portage, as beta2 and beta3 both > have a problem in the code parsing bios leading to problems with SSP on > hardened? > Why not use the live ebuild?
Becouse I missed that this was a "maintainer-needed"-package and hoped someone from gentoo would listen.
hhm, i updated nvclock to beta4 based on bug #260586 - i didnt see this bug. beta4 is now in the tree. please report any problems with in a new bug. Michał Górny: your patches look good. could you push them upstream? thanks kind regards Thilo
(In reply to comment #22) > Michał Górny: your patches look good. could you push them upstream? > thanks Just join #nvclock on FreeNode and talk to Thunderbird. He usually responds fast and is very helping. > kind regards > Thilo > Thanks for bumping the ebuild.
(In reply to comment #22) > Michał Górny: your patches look good. could you push them upstream? Done.
Maybe if our amd64 team is on board, something can actually be tested by the people who are both in the know and have the hardware. :)
(In reply to comment #24) > (In reply to comment #22) > > Michał Górny: your patches look good. could you push them upstream? > > Done. Please provide an ebuild diff starting from the current 0.8_beta4-r3.
OK, I've pushed an adapted live ebuild into the tree, but without the smartdimmer* patches (those should have been the topic of a new bug report anyway). I don't know if the current beta4 supports amd64 properly, but this bug is way too messy now - do file a new one for each remaining problem that is not already addressed in one of these nvclock bugs: Bug #265804: "media-video/nvclock-0.8_beta4-r3: needs 'X' use flag" Bug #266899: "media-video/nvclock-0.8_beta4-r3 sets incorrect backlight..." Bug #:
(In reply to comment #26) > Please provide an ebuild diff starting from the current 0.8_beta4-r3. 0.8_beta4-r3 works fine, no changes needed.
(In reply to comment #27) > I don't know if the current beta4 supports amd64 properly, but this > bug is way too messy now That happens sometimes when bugs gets (too?) old. Thank you for taking care of this and trying to sort out the mess!:-)
