Bug 287057 - korundum fails to build with ruby 1.9.3_p0
Summary: korundum fails to build with ruby 1.9.3_p0
Status: RESOLVED FIXED
Alias: None
Product: bindings
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kde-bindings
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-20 10:35 UTC by Andrea Scarpino
Modified: 2013-06-20 18:52 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.10.85
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrea Scarpino 2011-11-20 10:35:08 UTC
Version:           unspecified (using Devel) 
OS:                Linux

[ 19%] Building CXX object src/CMakeFiles/krubypluginfactory.dir/krubypluginfactory.o
Linking CXX shared module ../lib/krubypluginfactory.so
CMakeFiles/krubypluginfactory.dir/krubypluginfactory.o: In function `kdemain':
krubypluginfactory.cpp:(.text+0xbb4): undefined reference to `Init_prelude'
CMakeFiles/krubypluginfactory.dir/krubypluginfactory.o: In function `KRubyPluginFactory::create(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&)':
krubypluginfactory.cpp:(.text+0x1ec0): undefined reference to `Init_prelude'
collect2: ld returned 1 exit status
make[2]: *** [lib/krubypluginfactory.so] Error 1
make[1]: *** [src/CMakeFiles/krubypluginfactory.dir/all] Error 2
make: *** [all] Error 2

Reproducible: Always

Steps to Reproduce:
try to build it

Actual Results:  
build fails

Expected Results:  
build

KDE 4.7.80
ruby 1.9.3_p0
Comment 1 Stefano Crocco 2011-12-06 17:13:54 UTC
The problem here is that the function Init_prelude is hidden in ruby 1.9.3. I tried searching for an explanation for this change, but I couldn't find it. It seems that to allow compilation with ruby 1.9.3, the only solution is not to call Init_prelude. However, I'm not sure what this function does. The only hint I found with google is that it is used to setup the path for gems, but I don't know whether it is also needed for something else. However, here's a link to a thread in the ruby forum discussing a workaround for this: http://www.ruby-forum.com/topic/2323190
Comment 2 Johannes Huber 2013-06-20 17:34:40 UTC
Dear upstream, you can update the bug:

http://quickgit.kde.org/?p=korundum.git&a=commit&h=118c19ba70eadb353a8f19e4c86f38099416919c