On Saturday 17 November 2012, Laszlo Papp wrote: > > CMake says that it is processing the file > > /lib64/automoc4/Automoc4Config.cmake > > , not /usr/lib/automoc4/Automoc4Config.cmake (as pacman says). > > Is there maybe something with symbolic links ? > > Yes, so a quick workaround is getting a symlink from /bin/automoc4 to > /usr/bin/automoc4.
Yes, I think this is ok. > ls -lda /lib* > lrwxrwxrwx 1 root root 7 Oct 24 22:37 /lib -> usr/lib > lrwxrwxrwx 1 root root 7 Oct 24 22:37 /lib64 -> usr/lib >From Modules/UnixPaths.cmake: list(APPEND CMAKE_SYSTEM_PREFIX_PATH # Standard /usr/local /usr / ... ) I'm not too sure how the 64bit dirs are handled, but I guess that first cmake looks in /usr/local/lib64/, then in /usr/lib64/, then /lib64/ (where it finds the Config.cmake file), then proceeds without the suffix "64", i.e. /usr/local/lib/, /usr/lib/ and /lib/. It is somewhat strange /lib64/ is a symlink to /usr/lib/, but /bin/ is not such a symlink. Is there a reason for this ? This will probably break for more Config.cmake files, not only automoc. > I have just talked to the "automoc4" package maintainer for Archlinux in > #archlinux-bugs as there is a Bug Squashing Day today. He has this output: > > -- Automoc4Config: CURRENT_DIR: -/usr/lib/automoc4- current file: > -/usr/lib/automoc4/Automoc4Config.cmake- > -- Automoc4: bin dir: -/usr- exe: -/usr/bin/automoc4- > > Hence, certain people can reproduce this on Archlinux, but certain cannot. > The package maintainer has just written that to me, I am not the first one > having this issue on Archlinux, but he and others cannot reproduce it, > unfortunately. > > Do you have any ideas why it cannot find the same for me? Maybe the search order for the 64 bit dirs has been changed in 2.8.10, I don't know. Alex _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
