[fix failure to find libunwind on armhf] switch to cmake or autotools

[sten0]

[fix failure to find libunwind on armhf] switch to cmake or autotools

[WuBingzheng]

Thanks for post this.

I am not familiar with the package built system.
But it seems that libunwind is not installed in the system, because I see the following output which is not printed by my configure file:

 pbuilder-satisfydepends-dummy depends on libunwind-dev; however:
  Package libunwind-dev is not installed.

So would you like to make sure what's the problem? Is "libunwind not installed" or "installed but cat not detected by my hand-written configure" ?

I did not use autotools or cmake neither. I can not give you advice.
If that's useful to fix the problem, you are welcomed to add them.

[sten0]

Hi! Thank you for such a prompt reply :-) Yes, libunwind8 and libunwind-dev are installed. Here are the filelists:
https://packages.debian.org/sid/armhf/libunwind8/filelist
https://packages.debian.org/jessie/armhf/libunwind-dev/filelist

On the IRC channel #debian-mentors@oftc someone recommended adding autotools or cmake support as a way to prevent these kinds of issues--might be caused by changing binutils and gcc versions? The idea being do the work once and never worry about it again ;-) I'm leaning towards cmake, because it's simpler and because I don't think memleaks would benefit from autotools' extensive legacy (old UNIX systems) and non-Linux support...so I think it would be a lot more trouble for little gain. What do you think? P.S. Yes, I'm willing to learn how to add this support

[WuBingzheng]

Thanks for the improvement.

[morxa]

What's the status here? I'm currently looking into packaging memleax for Fedora, but the hand-written configure script is a blocker, as it doesn't accept some of the options that are passed by Fedora's %configure macro. A configure script based on autotools or a cmake setup would solve the issue.

[WuBingzheng]

I do not know the status.
Would you like to do this if you are familiar with autotools or cmake?

[sten0]

This is the guide I would use: *The Ultimate Guide to Modern CMake* ( https://rix0r.nl/blog/2015/08/13/cmake-guide ) I won't have time to work on this before September or October, so cannot volunteer at this time.

[WuBingzheng]

look forward to your work!