Add all dependencies to source prerequisites #2060
Conversation
I was trying to bootstrap the 2.0 tarball on an embedded system I was putting together and the configure script required more dependencies than the manual implies. It's entirely possible I'm doing something wrong though.
| @@ -28,6 +31,14 @@ | |||
| distribution does not provide these, you can obtain bzip2 from <link | |||
| xlink:href="http://www.bzip.org/"/>.</para></listitem> | |||
|
|
|||
| <listitem><para><literal>liblzma/literal>, which is provided by | |||
There was a problem hiding this comment.
I think you forgot a < before /literal>
| @@ -9,6 +9,9 @@ | |||
| <itemizedlist> | |||
|
|
|||
| <listitem><para>GNU Make.</para></listitem> | |||
|
|
|||
| <listitem><para>Bash Shell. Bash, and no other shell, is required to | |||
There was a problem hiding this comment.
"and no other shell" reads kind of oddly to me, can you say something like "the configure script relies on bashisms" or some such?
|
Thanks! Do you mind squashing these, or if I squash when I merge? |
|
I don't have the git repo downloaded right now, just the tarball. I made the edits over Github's interface and don't think I can squash commits with just the website. So if you could squash them while merging, that would be convenient, thanks. |
|
If this change is merged into master will it show up on the website soon or does it have to wait until the next release? If the latter, should it also get merged into the 2.0 branch? I wrote it in reaction to the 2.0 release tarball; if anyone else is building from the 2.0 source they might appreciate having the live manual agree with the configure script... |
I was trying to bootstrap the 2.0 tarball on an embedded system I was putting together and the configure script required more dependencies than the manual implies. It's entirely possible I'm doing something wrong though.