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.
Here is the code and error I recieve when trying to install bind
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- ./lib/isc/unix/socket.c.orig 2005-11-03 17:08:42.000000000 -0600 |+++ ./lib/isc/unix/socket.c 2006-02-18 13:09:15.000000000 -0600
--------------------------
Patching file lib/isc/unix/socket.c using Plan A...
Hunk #1 succeeded at 262 (offset 17 lines).
done
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- ./bin/named/include/named/globals.h.orig Sat Nov 24 17:47:59 2001
|+++ ./bin/named/include/named/globals.h Tue Feb 26 18:51:18 2002
--------------------------
Patching file bin/named/include/named/globals.h using Plan A...
Hunk #1 succeeded at 107 with fuzz 1 (offset 5 lines).
done
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- ./bin/named/named.8.orig 2007-01-29 18:23:44.000000000 -0600
|+++ ./bin/named/named.8 2007-06-07 23:17:33.000000000 -0500
--------------------------
Patching file bin/named/named.8 using Plan A...
Hunk #1 succeeded at 211 (offset 9 lines).
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- ./bin/named/lwresd.8.orig 2007-01-29 18:23:44.000000000 -0600
|+++ ./bin/named/lwresd.8 2007-06-07 23:17:18.000000000 -0500
--------------------------
Patching file bin/named/lwresd.8 using Plan A...
Hunk #1 succeeded at 204 (offset 49 lines).
done
checking build system type... i486-slackware-linux-gnu
checking host system type... i486-slackware-linux-gnu
checking whether make sets $(MAKE)... yes
checking for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether ln -s works... yes
checking for ar... /usr/bin/ar
checking for etags... /usr/bin/etags
checking for Exuberant Ctags etags... no
checking for perl5... no
checking for perl... /usr/bin/perl
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
bash-2.05# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/2.95.3/specs
gcc version 2.95.3 20010315 (release)
You may have to reinstall the gcc and binutils packages on that machine. You may want to also install/reinstall the gcc-g++ package (I don't know if bind uses C++ or C. If it's just C code, you shouldn't need the gcc-g++ package.)
yes the file binutils is in /var/log/packages. I have also completely rebuilt the OS same OS and everything else. Same error. If i use
ls -l /var/log/packages/binutils, no "-*" i get the following
-rw-r--r-- 1 root root 3010 Oct 14 06:04 /var/log/packages/binutils
Last edited by gymiv@aol.com; 10-18-2010 at 08:05 AM.
I didn't use Slackware way back when 8.0 was released, but I know the package naming format was significantly different (and you can see legacy code in the upgradepkg script). I believe /var/log/packages/binutils is the correct package log on Slackware 8.0, so if that file exists then it is indeed available on your system, and excluding a versioning problem, you should look elsewhere to find the problem.
would upgrading the package be a possible solution? If so how do igo about that. If not where do i go from here? Do you know of a walkthrough for configuring bind?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
