PDA

View Full Version : FC4t2 and Development Extras


wjdearborn
2005-04-18, 10:49 PM CDT
FC4t2 loaded with absolutely no problems on my Intel D865PERL motherboard which is operating in a multi-boot mode with XP and FC3 as well as FC4t2. Probelms emerge when I attempt to use the Extras repo for another program. As of this AM yum has updated my system to the current development version.

My problem emerges when I attempt to use yum to install audacity (I need to work on a sound file). yum brought in audacity but running the program lead to the error: that the shared library libsndfile.so.1 could not be found. I used yum again to install libsndfile.so.1 now I get a symbol lookup error: /usr/lib/libwx_gtk2-2.4.so.0: undefined symbol: _ZTV11wxFileProto.

I was under the impression that Extras are supposed to just load and run - with no problems. Should these two problems be reported in Bugzilla - or is the development Extras simply not ready for prime time and I should just sit back and wait? :confused:

Is there a work around for the current undefined sysmbol?

Bill (wjdearborn)

cybrjackle
2005-04-19, 08:11 AM CDT
FC4t2 loaded with absolutely no problems on my Intel D865PERL motherboard which is operating in a multi-boot mode with XP and FC3 as well as FC4t2. Probelms emerge when I attempt to use the Extras repo for another program. As of this AM yum has updated my system to the current development version.

My problem emerges when I attempt to use yum to install audacity (I need to work on a sound file). yum brought in audacity but running the program lead to the error: that the shared library libsndfile.so.1 could not be found. I used yum again to install libsndfile.so.1 now I get a symbol lookup error: /usr/lib/libwx_gtk2-2.4.so.0: undefined symbol: _ZTV11wxFileProto.

I was under the impression that Extras are supposed to just load and run - with no problems. Should these two problems be reported in Bugzilla - or is the development Extras simply not ready for prime time and I should just sit back and wait? :confused:

Is there a work around for the current undefined sysmbol?

Bill (wjdearborn)

Your impression is a loaded one :D

This is "devel" release, and so is extra's so there will be bugs and problems:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=155142

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154958