Partitionmanager cmake script looks if ped_file_system_resize function is available in libparted and if it is found then cmake enables FAT32 support in partitionmanager. When I run "emerge partitionmanager" I can see in the output -- Looking for ped_file_system_resize -- Looking for ped_file_system_resize - not found However, if I download partitionmanager source and run "cmake .." then I get -- Looking for ped_file_system_resize -- Looking for ped_file_system_resize - found Expected results: emerged ebuild behaves in the same way as normal out of tree build. FAT32 resize is enabled in partitionmanager Actual results: FAT32 resize support is disabled.
Which version of partitionmanager are you using?
(In reply to Michael Palimaka (kensington) from comment #1) > Which version of partitionmanager are you using? Sorry, I forgot to mention but it is 1.0.3_p20130623. Actually, the older ebuild does not work at all due to missing udisks2 support.
I can confirm, but I don't know what the cause is. Running cmake manually but using the same arguments passed by portage does not reproduce the issue.
Seems fixed in the meantime. Can you please confirm? Current emerge output on ~amd64 > -- Looking for ped_file_system_resize > -- Looking for ped_file_system_resize - found
I don't have ~amd64, only stable so I can't test at the moment. Any idea what unstable package might fix it. I've checked and it is not cmake
Working here now on stable.
(In reply to Michael Palimaka (kensington) from comment #6) > Working here now on stable. It is not working here on amd64 stable. Strange...
It still doesn't work on both KDELibs4 and KF5 versions. If I build using portage I still get -- Looking for ped_file_system_clobber -- Looking for ped_file_system_clobber - not found -- Looking for ped_file_system_resize -- Looking for ped_file_system_resize - not found And manually using cmake -- Looking for ped_file_system_clobber -- Looking for ped_file_system_clobber - not found -- Looking for ped_file_system_resize -- Looking for ped_file_system_resize - found
I can reproduce in portage, and reproduce manually by sourcing the build's environment.
(In reply to Michael Palimaka (kensington) from comment #9) > I can reproduce in portage, and reproduce manually by sourcing the build's > environment. to be more precise: declare -x LDFLAGS="-Wl,-O1 -Wl,--as-needed"
Created attachment 395460 [details, diff] patch to fix issue
(In reply to Karol Herbst from comment #11) > Created attachment 395460 [details, diff] [details, diff] > patch to fix issue Applied upstream http://commits.kde.org/partitionmanager/dd59ed858163482841aab82f7c4ef96e3a385bb6
For future reference, apparently the failure was caused because the linking order for the feature check looked liks this: "... -lparted -lparted-fs-resize ...". Since the feature check uses functions from parted-fs-resize only, --as-needed throws away -lparted. This causes undefined symbol errors since parted-fs-resize needs parted.
Andrius, I was going to do a snapshot to fix this issue in-tree, but it looks like partitionmanager has disappeared from releaseme?