Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#47404 - Potential Ogre packaging issue

Attached to Project: Arch Linux
Opened by Marc-Olivier Barre (mobarre) - Wednesday, 16 December 2015, 09:14 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 16 December 2015, 19:13 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have community/ogre 1.9.0-12 installed on my system and for some obscure reasons, it looks broken.

A detailed explanation of what exactly is happening is in this post on the ogre forum: http://www.ogre3d.org/forums/viewtopic.php?f=2&t=80897

Problem can be reproduced by installing the ogre 1.9 packages and trying to compile the example source code from here: https://github.com/ogre3d/clean-project

Any chance this could be some bizarre packaging issue ?
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 16 December 2015, 19:13 GMT
Reason for closing:  Not a bug
Comment by Marc-Olivier Barre (mobarre) - Wednesday, 16 December 2015, 18:39 GMT
New hint, but different outcome: I tried rebuilding the ogre package from the PKGBUILD file of the community repo. The build fails miserably in the linking phase of the Samples. Something is wrong there.

Note: I did not tweak my build chain. I would understand that this question could come up. Also, I have a few packages from AUR, but none too serious or related to build/linking issues.

Only thing that "might" introduce weirdness in my setup is the fact that I use some 32bit libs (through official packages only) on my 64 bit system, mainly to run steam.

Could it be the lib32 packages I use that mess up my tool chain or something ? (shooting in the dark here).
Comment by Marc-Olivier Barre (mobarre) - Wednesday, 16 December 2015, 18:53 GMT
For the record, the Ogre package build ends like this:

[100%] Linking CXX executable ../../bin/SampleBrowser
CMakeFiles/SampleBrowser.dir/src/SampleBrowser.cpp.o: In function `OgreBites::SampleContext::createInputDevices()':
SampleBrowser.cpp:(.text._ZN9OgreBites13SampleContext18createInputDevicesEv[_ZN9OgreBites13SampleContext18createInputDevicesEv]+0x4b): undefined reference to `OIS::InputManager::createInputObject(OIS::Type, bool, std::string const&)'
SampleBrowser.cpp:(.text._ZN9OgreBites13SampleContext18createInputDevicesEv[_ZN9OgreBites13SampleContext18createInputDevicesEv]+0x8c): undefined reference to `OIS::InputManager::createInputObject(OIS::Type, bool, std::string const&)'
CMakeFiles/SampleBrowser.dir/src/SampleBrowser.cpp.o: In function `OgreBites::SampleContext::setupInput(bool)':
SampleBrowser.cpp:(.text._ZN9OgreBites13SampleContext10setupInputEb[_ZN9OgreBites13SampleContext10setupInputEb]+0x46d): undefined reference to `OIS::InputManager::createInputSystem(std::multimap<std::string, std::string, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >&)'
collect2: error: ld returned 1 exit status
Samples/Browser/CMakeFiles/SampleBrowser.dir/build.make:113: recipe for target 'bin/SampleBrowser' failed
make[2]: *** [bin/SampleBrowser] Error 1
CMakeFiles/Makefile2:3660: recipe for target 'Samples/Browser/CMakeFiles/SampleBrowser.dir/all' failed
make[1]: *** [Samples/Browser/CMakeFiles/SampleBrowser.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2


My opinion is that this should not happen on a sane system. I'm going to run some more tests on a docker contained archlinux with various flavors of setups. Might come up with something.
Comment by Doug Newgard (Scimmia) - Wednesday, 16 December 2015, 19:12 GMT
I just built ogre in a clean chroot without any problems. This tells me that the problem is on your system, not with the package. Are you sure it's linking to what you think it is?

Anyway, since this isn't a packaging issue, I'm going to close this. Feel free to ask for help you the mailing lists, forums, or IRC.

Loading...