LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (http://www.linuxquestions.org/questions/linux-general-1/)
-   -   How do I compile dev packages? (specifically python-dev) (http://www.linuxquestions.org/questions/linux-general-1/how-do-i-compile-dev-packages-specifically-python-dev-808453/)

Axelman0 05-17-2010 06:44 PM

How do I compile dev packages? (specifically python-dev)
 
I just compiled python 2.6.5 from source. I also need the python C header files, which would normally be easy to get but I'm on day one of my migration to Slackware so I don't know how to go about getting them. I'd like to compile them myself if possible.

lumak 05-17-2010 09:15 PM

You don't. the -dev packages are designed to go with the other packages of the same version. That is, if you install python and want to compile something that uses python's libs, you must install the same version python-dev from the repository.

If you are upgrading to an unsupported and conflicting version of python, you must uninstall any python currently on your system and compile your new version from source.


A -dev package are the header files removed from the main packaged to save a few mega bytes of data. Honestly, this system that popular distros insist on doing only cause confusion and irritation from those that want to compile their own software. In Slackware, the header files are included in the main package and there are no -dev pacakges because they are not needed.


But because of your distro, if you want to compile python from source, you will now have to install the -dev pacakges of everything python depends on. Good luck with that.

BTW, how much storage space are these distros saving you at the cost of your sanity? only about 300M. Yes. on your 80gig+ hard drive, they save you 300M at the cost of your sanity when trying to compile your own software.

EDIT:
Also, Python is one of those things you probably shouldn't update from source without good cause. It's really best to use the packages in your official repository.
Other things you should never think of updating are gnome, gnome libs, kde, kde libs, gtk, qt, tool chain (compiler and other tools), and the kernel because the major players (tool chain) and ancillary modules are based off that kernel supported by your distro

exvor 05-17-2010 10:09 PM

Quote:

and the kernel because the major players (tool chain) and ancillary modules are based off that kernel supported by your distro
This again is because distros are doing exactly what kernel devs tell them not to. Using unsanitized headers from the kernel......

I manually update my kernel via compile all the time and it never breaks any of my tool chain (because its not supposed to when done correctly).

Axelman0 05-17-2010 10:33 PM

Thank you for the explanation lumak. I've just moved to Slackware from Ubuntu so alot of this stuff is new to me. I compiled the production version of python (2.6.5) mostly for fun, since I hadn't compiled anything in my new setup yet and I knew I'd be using Python (Slackware 13 had came with a slightly older version). Not having to worry about dev packages anymore will make things much simpler.


All times are GMT -5. The time now is 07:01 PM.