#294 closed defect (invalid)
why rm + cp libbz2.a during chapter 06-bzip2
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Book | Version: | CVS |
| Severity: | normal | Keywords: | |
| Cc: |
Description
I'm wondering about:
rm /usr/lib/libbz2.a && cp libbz2.a /usr/lib &&
a 'cp' would overwrite the existing file so why do we 'rm' it?
Change History (4)
comment:1 by , 23 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 23 years ago
| Resolution: | → invalid |
|---|---|
| Status: | assigned → closed |
comment:3 by , 23 years ago
While confirming this bug, I came up with the following problem. We still have the following text in the bzip2 ch6 installation: "The reason we don't use make install is that bzip2's make install doesn't install the shared libbz2.so, nor the bzip2 binary that's linked against that library. So we have no choice but to manually install the files. " but we DO now use make install. I'm not changing the book (due to CVS freeze), Gerard, you might want to alter this then CLOSE this bug before LFS-3.3.
comment:4 by , 23 years ago
Removed the paragraph altogether. I'm sure people can figure it out for themselves. The command explanations are a bit of a general mess which need cleaning up anyways (hopefully for lfs-4.0 would be nice), so this will be made nicer in time.
the make install that was recently added fixed the need to cp+rm libbz2.a