LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Compiling glibc using slackbuild (http://www.linuxquestions.org/questions/slackware-14/compiling-glibc-using-slackbuild-835822/)

alekow 10-02-2010 01:24 PM

Compiling glibc using slackbuild
 
Hi!

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

Can anyone tell me what am I doing wrong?

Thanks in advance.

GrapefruiTgirl 10-02-2010 01:31 PM

Did you run ./configure before running `make`?

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.

alekow 10-02-2010 03:01 PM

Quote:

It appears that a SlackBuild script is not being used here.
It IS being used.
Quote:

maybe showing us the exact sequence of commands you're running before this happens
Code:

# ./glibc.SlackBuild
Or to be completely exact:
Code:

LC_ALL=C LANG=C ./glibc.SlackBuild
just to produce english output, because i use localized system.
Quote:

Please have a look at the SlackBuild script - that will learn you some stuff you will want to know.
Well, I do want to learn, so i looked there to before running it :-)

BrZ 10-03-2010 01:59 PM

???
Quote:

../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.

alekow 10-03-2010 02:20 PM

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:

http://bugs.gentoo.org/86771

But it doesn't help me at all.

If someone using slackware-current or slackware-13.1 simply ran glibc slackbuild, and than report what happenned - it could be of some use to me.

Thanks for your replies.

BrZ 10-03-2010 02:30 PM

current64, gcc-4.4.5: http://pastebin.com/ib58YxdN

Edit: That was for gcc. Sorry...

alekow 10-03-2010 05:02 PM

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.

BrZ 10-03-2010 05:14 PM

1 Attachment(s)
Sorry friend,gcc is still going, but I can confirm that glibc-2.12.1 built fine here...

alekow 10-04-2010 01:15 AM

Well, that's... good. Anyone with 32-bit? Maybe current?

Squall90 10-04-2010 11:05 AM

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?^^

GrapefruiTgirl 10-04-2010 11:49 AM

Depends. :)

If you wished to install it, do:
Code:

installpkg <package-name-you-just-made>
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. :)

Squall90 10-04-2010 02:51 PM

@GrapefruiTgirl thanks for you answer, but I just build it because alekow wanted someone to do so. (And I wanted to try out my new CPU.) ^^

alekow 10-04-2010 02:54 PM

Quote:

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...

GrapefruiTgirl 10-04-2010 02:55 PM

Oops! I thought I was replying to the OP! Sorry folks for the confusion! :p

Squall90 10-04-2010 03:37 PM

Quote:

Originally Posted by alekow (Post 4117502)
Nope, exactly the same error, so it's not it. A hardware problem maybe??? It get's boring...

And you have a full installation? This is really weird.
Which user do you use when you run SlackBuilds?


All times are GMT -5. The time now is 06:26 AM.