SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Meh...my mistake...I should have said it was the build from slackbuilds.org. But, I'll try it on the source tarball for that slackbuild and see what happens.
Seems the libiconv package is interfering with mono to cause this. I took a quick look at the slackbuild and suggest you add
the following line (in green) right after the configure block and before the make command (just before line 64):
Code:
--build=$ARCH-slackware-linux
sed -i -e 's|#define HAVE_LOCALCHARSET_H 1|/* #undef HAVE_LOCALCHARSET_H */|' eglib/config.h
make
make install DESTDIR=$PKG
--mancha
*Note: Alternatively, you could removepkg the libiconv package; build & install the mono package; and then re-install libiconv.
That last suggestion did the trick. It built this time and on the 2.11.4 also.
I should mention maybe, that before your suggestion, during the 'config' it would always stop at an 'ltoptions.m4' part and wouild sit there for a minimum of 1 minute before finally carrying on and then eventually to the failure problem. This time though, it did not stop at that part and went right on through everything.
Thank you for the assistance!
PS
If you're wondering why I want/need mono on my linux system, it's to try out this little app here
I'm not a programmer, so that and even the sed command thing left me scratching my head...it just worked is all I saw, heh. Maybe you bartgymnast or you mancha, should get in touch with the maintainer of the mono build and discuss it with him, as I wouldn't know what to tell him or why I was saying it. Whatcha think?
mono defaults to building static libs; --enable-static is unnecessary.
mono defaults to the system installed libgdiplus and detection works fine here. Is there a particular setup on your machine that requires specifying a path?
Note: you can test your installed mono by running /usr/bin/mono-test-install. If you get "Your have a working System.Drawing setup" then mono is using your system libgdiplus correctly (n.b. their typo, not mine).
mono defaults to using $(libdir)/pkgconfig for its pkgconfigdir and the SBo SlackBuild seemingly sets $(libdir) appropriately for Slack-64. If it indeed fails on your Slackware-64 system, I suggest you contact the SBo mono maintainer directly.
Quote:
Originally Posted by bartgymnast
Also, it might be good to reconf before configure.
libtoolize --copy --force
autoreconf -vif
than there should be no need for the sed command.
Re-libtoolizing and re-generating configuration files does not solve irgunII's problem. The sed command would still be needed.
The sed command solved your issue hackishly. Basically, mono believes (correctly) it can use locale_charset() on your system
because you have installed libiconv. Unfortunately, it was not linking properly.
Given how appreciative you've been on this thread and since I had already downloaded mono in order to assist you, I decided to
invest a little more time to develop a fix.
Rather than adding the sed line to mono.Slackbuild, you could do the following instead:
Note: the current solution you're using (with sed) is effectively running a version of mono as it would build if you didn't have the libiconv
package installed on your system.
Hey great! Thanks for that, as I feel better knowing I've not taken/deleted something off my system just to install another something (mainly because I'd forget in 10 seconds that I'd deleted the first something and would scratch my head wondering why all of a sudden other apps and stuff weren't working correctly anymore, heh...ADD really sucks, especially at 51).
I also e-mailed the maintainer and asked him to take a look at this thread and see what he thinks he ought to do about it not building. Maybe he'll take up your 'patch' and simply use it. That'd be cool.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.