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.
Im trying to recompile glibc from a working slackware-current system using source from a slackware mirror. I'm doing it for testing purpose only. Never done that before, so i'm not sure if i'm doing it right. I get the following error:
Code:
make[2]: Entering directory `/glibc-tmp-a44be92860d34519b0c9a4500878e2e6/glibc-2.11.1/iconvdata'
../Makeconfig:85: ../i486/config.make: No such file or directory
/bin/sh: line 0: cd: ../i486: No such file or directory
The GNU C library has not been configured.
Run `configure' to configure it before building.
Try `configure --help' for more details.
make[2]: *** No rule to make target `../i486/config.status', needed by `../i486/config.make'. Stop.
make[2]: Leaving directory `/glibc-tmp-a44be92860d34519b0c9a4500878e2e6/glibc-2.11.1/iconvdata'
make[1]: *** [iconvdata/subdir_lib] Error 2
make[1]: Leaving directory `/glibc-tmp-a44be92860d34519b0c9a4500878e2e6/glibc-2.11.1'
make: *** [all] Error 2
make -r PARALLELMFLAGS="" CVSOPTS="" -C .. objdir=`pwd` all
make[1]: Entering directory `/glibc-tmp-a44be92860d34519b0c9a4500878e2e6/glibc-2.11.1'
make subdir=csu -C csu ..=../ subdir_lib
make[2]: Entering directory `/glibc-tmp-a44be92860d34519b0c9a4500878e2e6/glibc-2.11.1/csu'
make[2]: Leaving directory `/glibc-tmp-a44be92860d34519b0c9a4500878e2e6/glibc-2.11.1/csu'
make[2]: Entering directory `/glibc-tmp-a44be92860d34519b0c9a4500878e2e6/glibc-2.11.1/csu'
../Makeconfig:85: ../i486/config.make: No such file or directory
/bin/sh: line 0: cd: ../i486: No such file or directory
The GNU C library has not been configured.
Run `configure' to configure it before building.
Try `configure --help' for more details.
make[2]: *** No rule to make target `../i486/config.status', needed by `../i486/config.make'. Stop.
make[2]: Leaving directory `/glibc-tmp-a44be92860d34519b0c9a4500878e2e6/glibc-2.11.1/csu'
make[1]: *** [csu/subdir_lib] Error 2
make[1]: Leaving directory `/glibc-tmp-a44be92860d34519b0c9a4500878e2e6/glibc-2.11.1'
make: *** [all] Error 2
I suggest examining the SlackBuild script from the CD or DVD or from a mirror, and look at the options given to the configure script first too, so you end up with a working glibc that's properly configured for Slackware.
Also note that using the `configure` + `make` + `make install` method will not produce a Slackware package, AND it will (if done as root especially) overwrite some or all of your working glibc on your system, unless you're safely inside a chrooted build environment, so you very likely DO NOT want to run `make install`. For learning purposes, run `configure` and `make` only.
Please have a look at the SlackBuild script - that will learn you some stuff you will want to know.
EDIT - I see (upon opening my eyes and re-reading!) your thread title says "..slackbuild.." so maybe showing us the exact sequence of commands you're running before this happens, will indicate something wrong. It appears that a SlackBuild script is not being used here.
Last edited by GrapefruiTgirl; 10-02-2010 at 12:37 PM.
../Makeconfig:85: ../i486/config.make: No such file or directory
/bin/sh: line 0: cd: ../i486: No such file or directory
The GNU C library has not been configured.
Run `configure' to configure it before building.
Well, i'm surprised too, because configure is definitely being run by the slackbuild script! Any ideas? I've found only one similar error - on gentoo bugzilla, here's a link:
So, could you try with glibc and see if it creates a package? It did compile for me for some time... The error occured while compiling iconvdata, which is not the first part of code.
HOWEVER: You already have this package installed, so theoretically, you would want to upgrade the package. Notice the % sign in the middle. Format is: upgradepkg oldpkg%newpkg
Code:
upgradepkg glibc%</path/to/your/new/package>
HOWEVER #TWO: Again, you already have this installed, so theoretically you don't really want to install this anyhow.. If there's anything wrong with your new package, then installing it might bork your system.
But, for learning purposes, if that's what this is, then use `installpkg` or `upgradepkg` and see what happens.
Using the glibc.SlackBuild from the Slackware 13.1 (32bit) DVD I created glibc-2.11.1-i486 with GCC 4.4.4.
Now what?^^
Then I guess something must be wrong with my slackware source tree, or i don't know... Tried compiling it on slackware-current and a clean installation of 13.1 with the same result... I'll re-download the source and try one more time ;-)
________________________
EDIT:
Nope, exactly the same error, so it's not it. A hardware problem maybe??? It get's boring...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
