Project

General

Profile

Actions

Emulator Issues #3273

closed

Cg nvidia toolkit not found

Added by bonanit about 14 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

I'm trying to install Dolphin from svn in a x86 Gentoo with the ebuild in http://bugs.gentoo.org/show_bug.cgi?id=281543

However, I cannot get past the nvidia cg toolkit detection. I've tried with the cg version in portage (which installs in /opt) and with the one in the bug (which installs in /usr) with no success. I even tried the updated build from this bug http://bugs.gentoo.org/show_bug.cgi?id=261481 with no success.

Is there any problem with the current build? How does scons try to detect those libs? I'm not familiar with this build system, so I would appreciate any hint in solving this. Thanks.

Actions #1

Updated by nitro322 about 14 years ago

FYI, I'm running Gentoo as well and have been testing Dolphin lately. The -r4 ebuild from that post mostly works, but I'm currently working on a much improved -r5, which should be done tonight. Unless you're in a great rush, I recommend waiting for that new ebuild before spending much time troubleshooting -r4.

As for your specific cg issue... which version of GCC are you using? Run "gcc-config -c" if you're not sure. I ran into the cg problem you described when using GCC 4.3.4 to test something. Using GCC 4.4.3, though (the current stable version), worked perfectly fine. If you're still using 4.3.4, try switching to 4.4.3 and try again. You can follow the instructions here to upgrade:
http://www.gentoo.org/doc/en/gcc-upgrading.xml

Actions #2

Updated by bonanit about 14 years ago

Man, that was fast! Indeed I'm using gcc 4.3.4, because I don't usually upgrade unless I find a reason to. Looks like I have one now.

Anyway, I'll both update gcc and wait for your new ebuild. I guess you'll post it on the bug. I'll give it a try once it's there.

As a side note, I don't know if you're the developer that wrote on the bug who's interested in including Dolphin into portage. Perhaps it's a good idea to put it in sunrise as a first step? I could try and help on that.

Many thanks!

Actions #3

Updated by nitro322 about 14 years ago

Nah, I'm not a developer at all. Just happened to be testing Dolphin on Gentoo over the last few nights and saw your bug report while searching for something else and figured I'd give you a heads up.

Here's a tip, though: if you do upgrade to 4.4.3 and get dolphin working, DO NOT rebuild wxGTK. I made the mistake of doing that on my system and now I can no longer compile dolphin on my desktop (the full depressing details are in bug 3268). Once you do get it working, just leave it alone and be happy with it. :-)

Actions #4

Updated by bonanit about 14 years ago

Ok, I'm still unsure what exactly prevented scons from detecting cg, but this was solved with the gcc switch and rebuild of the system with it, so this bug can be closed.

Actions #5

Updated by BhaaL about 14 years ago

The scons detection problem has been around for quite long, and it seems to be hard to just get-it-right(TM).
Whenever the cg check fails and you have it installed, another of the linked components fails this check. See http://code.google.com/p/dolphin-emu/source/browse/trunk/SconsTests/utils.py for information, CheckPKG simply tries to build a small piece of code with the given flags - most likely, your wxGTK is broken and fails this test @nitro

Actions #6

Updated by Anonymous over 13 years ago

  • Status changed from New to Fixed

Ignore this...Status:Verified was removed, changing to Fixed

Actions

Also available in: Atom PDF