Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 255373 - kde-misc/knetworkmanager-0.2.2_p20080528 cannot compile
Summary: kde-misc/knetworkmanager-0.2.2_p20080528 cannot compile
Status: RESOLVED DUPLICATE of bug 253788
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo KDE team
Depends on:
Reported: 2009-01-18 12:49 UTC by Tom Barbette
Modified: 2009-01-23 15:56 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

build.log (build.log,35.80 KB, text/plain)
2009-01-18 12:50 UTC, Tom Barbette
environment (environment,171.97 KB, text/plain)
2009-01-18 12:51 UTC, Tom Barbette

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Barbette 2009-01-18 12:49:23 UTC
I have been tryed to emerge knetworkmanager for 2 days... With many recompilations of entire kde meta package... but never works.
I have the same bug with previous versions.

Reproducible: Always

Steps to Reproduce:
1.emerge knetworkmanager

Actual Results:  
make: *** [all] Erreur 2                                                                                 
 * ERROR: kde-misc/knetworkmanager-0.2.2_p20080528 failed.                                               
 * Call stack:                                                                                           
 *     , line   49:  Called src_compile                                               
 *             environment, line 4199:  Called kde_src_compile                                           
 *             environment, line 3011:  Called kde_src_compile 'all'                                     
 *             environment, line 3136:  Called kde_src_compile 'myconf' 'configure' 'make'               
 *             environment, line 3132:  Called die                                                       
 * The specific snippet of code:                                                                         
 *                   emake || die "died running emake, $FUNCNAME:make"
 *  The die message:
 *   died running emake, kde_src_compile:make
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/kde-misc/knetworkmanager-0.2.2_p20080528/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/kde-misc/knetworkmanager-0.2.2_p20080528/temp/environment'.

>>> Failed to emerge kde-misc/knetworkmanager-0.2.2_p20080528, Log file:

>>>  '/var/tmp/portage/kde-misc/knetworkmanager-0.2.2_p20080528/temp/build.log'

Expected Results:  
Emerged successfully

I'm using kde 4, but I have kdelibs-3 for compatibility of programs like this.
Comment 1 Tom Barbette 2009-01-18 12:50:54 UTC
Created attachment 178875 [details]
Comment 2 Tom Barbette 2009-01-18 12:51:13 UTC
Created attachment 178877 [details]
Comment 3 Carlos Cordoba 2009-01-23 13:17:08 UTC
This seems to happen because you are using Networkmanager 0.7 and current knetworkmanager version in portage doesn't have support for it.

I've found in you build log this part:

knetworkmanager-encryption.h:35:35: error: NetworkManager/cipher.h: No such file or directory
knetworkmanager-encryption.h:36:45: error: NetworkManager/cipher-wep-ascii.h: No such file or directory
knetworkmanager-encryption.h:37:43: error: NetworkManager/cipher-wep-hex.h: No such file or directory
knetworkmanager-encryption.h:38:50: error: NetworkManager/cipher-wep-passphrase.h: No such file or directory
knetworkmanager-encryption.h:39:47: error: NetworkManager/cipher-wpa-psk-hex.h: No such file or directory
knetworkmanager-encryption.h:40:54: error: NetworkManager/cipher-wpa-psk-passphrase.h: No such file or directory

Compare it to bug #253788. Hope this helps
Comment 4 Tom Barbette 2009-01-23 15:56:01 UTC
Yep, fixed.
But the downgrade solution is not very cool... I'll wait for the kde plasma plugin and use wicd until this time.

Thanks a lot!

*** This bug has been marked as a duplicate of bug 253788 ***