![]() |
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'Thanks in advance. |
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. |
Quote:
Quote:
Code:
# ./glibc.SlackBuildCode:
LC_ALL=C LANG=C ./glibc.SlackBuildQuote:
|
???
Quote:
|
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. |
|
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.
|
1 Attachment(s)
Sorry friend,gcc is still going, but I can confirm that glibc-2.12.1 built fine here...
|
Well, that's... good. Anyone with 32-bit? Maybe current?
|
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?^^ |
Depends. :)
If you wished to install it, do: Code:
installpkg <package-name-you-just-made>Code:
upgradepkg glibc%</path/to/your/new/package>But, for learning purposes, if that's what this is, then use `installpkg` or `upgradepkg` and see what happens. :) |
@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.) ^^
|
Quote:
________________________ EDIT: Nope, exactly the same error, so it's not it. A hardware problem maybe??? It get's boring... |
Oops! I thought I was replying to the OP! Sorry folks for the confusion! :p
|
Quote:
Which user do you use when you run SlackBuilds? |
| All times are GMT -5. The time now is 11:30 AM. |