Trying to compile Glibc-2.7 with src2pkg-1.93 on Slamd64-current.
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.
Trying to compile Glibc-2.7 with src2pkg-1.93 on Slamd64-current.
Does anyone know why this is the only output I get from running a compile of Glibc-2.7 with src2pkg-1.93. I am trying to create a generic build of Glibc for testing purposes. I also need to become aware of the intricacies of building Glibc. I am obviously missing something. So if someone can explain the proper way of writing my glibc.src2pkg file, I would really appreciate it.
Gzipping glibc-2.7-x86_64-1DIST.tar to glibc-2.7-x86_64-1DIST.tar.gz
Renaming glibc-2.7-x86_64-1DIST.tar.gz to glibc-2.7-x86_64-1DIST.tgz
Moving glibc-2.7-x86_64-1DIST.tgz to /usr/src/DIST/PACKAGES
You probably _don't_ want to compile something like glibc with src2pkg - especially on Slamd64, where we're also doing the necessary magic to add in for 32 bit support.
In this case, you are better off just tweaking the glibc.SlackBuild as required to your needs.
I agree -sort of. When building gcc or glibc there are many tweaks which need to be done which don't fit into the 'normal' scheme of compiling and building packages. However, src2pgk works fine as a framework for making the build easier to script and repeat. I usually 'port' such builds to the src2pkg format by just commenting out a couple of the src2pkg commands for configuring, compiling and installing and paste in the code from the SlackBuild. Only minor modifications are needed to make this work and you can even create multiple packages from the same source tarball or one package from mulitple sources.
I've tried compiling ncurses with src2pkg. Each time I do, what I get is the source files being packed, instead of the files which have been compiled. Any ideas on how to change this outcome?
Gzipping ncurses-5.6-x86_64-1DIST.tgz.tar to ncurses-5.6-x86_64-1DIST.tgz.tar.gz
Renaming ncurses-5.6-x86_64-1DIST.tgz.tar.gz to ncurses-5.6-x86_64-1DIST.tgz
Moving ncurses-5.6-x86_64-1DIST.tgz to /usr/src/DIST/PACKAGES
I'll try to help you on this one within a couple of days.
Not to imply in anyway that I am tired of saying thanks. Because I realize that I have asked for a lot from you, and taken a good deal of your time. So the fact that you're still willing to help, is gratifying. I posted something after this original one. I forgot to post it right away. I think I was trying to figure some stuff out on my own. But that didn't get anywhere. So I am thinking that my learning whatever you will have to share, will help with that as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.