Compiling and linking question
To my understanding, when you compile a package, it may link to other packages already installed. I'm not sure what this linking means other then the package being compiled knows this other package is there and now expects it to be there when it runs.
The main question is, say I compile packageB. PackageB sees packageA that's already installed. Now I need to recompile packageA. Do I also need to recompile pacageB because packageA has changed? Thanks! |
it depends on the changes to the package you are linked against, usually a minor revision change will not cause a problem, if there is a major version change then you may have to recompile packages that are linked against the one you are updating, if you need to do this it will be in the README or CHANGELOG files, you may be lucky that the part of the library you need to use has not changed or if it has changed too much or gone away altogether the app linked sgainst the library may just segfault with no warning.
The moral of this is read the documentation and if in doubt 'suck it and see'. |
Quote:
|
Is there a simple way to know what packages are linked to the package you want to replace with a newer version? I can see how this can get out of hand quickly because these other packages may be linked into other packages as well.
|
Quote:
Seriously one of the main drawbacks of LFS is no dependency checking, but then again the system can't update anything by itself ( unlike the aforementioned 'Linux for dummies' distro ), so if you are going to update a library etc its up to you to make sure it doesn't break anything and to update anything that you need to, with (B)LFS you are the boss! |
What you could do is use a dependency tree.
Check for each package what it requires according to the book and what you installed of the recommended stuff. A lot of work and sometimes some packages get new dependencies or new packages arise. |
Thanks for all the info guys! I really appreciate it.
|
All times are GMT -5. The time now is 03:56 PM. |