[SOLVED] Dependencies for installing slackbuilds on barebones linode
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I wasn't able to apply the patch, I got "hunk failed" for each of the hunks in the patch. I tried applying it by manually editing the source files, and it looks like the source I have doesn't match up with the patch. This would make sense, as the patch is from (I think) 2010 and nginx 1.4.1 was released in 2013.
I also tried setting CFLAGS="" before running configure without success.
I'm actually a little confused as to why I'd need a patch to start out with, since I was able to install the same slackbuild on 2 different stock Slackware64 systems. They were normal installs though, not the stripped down version you get with Linode. So, I think I'm just missing some dependencies.
I do have glibc installed, but it's still not able to find uint64_t for some reason.
Any ideas how I can get a linode updated with the necessary dependencies?
Actually.... it looks like stdint.h exists on my system, *and* defines uint64_t. Any idea why nginx can't find it?
# grep "uint64" `find /usr/include/ -name "stdint.h"`
/usr/include/stdint.h:typedef unsigned long int uint64_t;
/usr/include/stdint.h:typedef unsigned long long int uint64_t;
After a closer look at objs/autoconf.err I see that it seems to be missing linux/limits.h:
checking for uint64_t
In file included from /usr/include/bits/posix1_lim.h:160:0,
/usr/include/bits/local_lim.h:38:26: fatal error: linux/limits.h: No such file or directory
I've also just recently set up my Slackware Linode and noticed they leave out a lot of packages. In order to get to a full Slack install I just did
root@hades:~ # slackpkg install a/*
And so on for every package set (xap, l, n, etc). After doing this, I haven't experienced any problems compiling or running software. My /var/log/packages shows around 620 packages I believe, so that's a good guideline if you want to get up to a full Slackware install.