| Newsgroups |
gmane.network.tin.user |
| Organization |
Enturbulators 'R' Us |
| Message-ID |
<007701c3b146$3c44ba30$11611e43@zamboni2k> |
Thomas Dickey <[email protected]> wrote:
> as a rule, when I'm looking at a package, I
>
> + first look to see if it has a configure script
>
> (if not, look for a "Makefile", and do a "make -n", though the
> last one of those I looked at was junk - "make -n" started doing
> the configure & compile ;-)
What does '-n' do here? Trial output with no actual compilation?
Dependency check?
> + take a look at the head of that to see if it has been generated
> by autoconf. If so, do "./configure --help" to see what it
> might allow. (If it's not that simple - handcrafted configure
> scripts, have to _read_ the documentation first).
reading != comprehending.
> + try a "./configure". If there are no warnings, etc.,
Ran it. Nothing memorable in the output. (That isn't to say there was
nothing important there, mind you... I probably did miss something.)
> + try a "make -n". Look at the warnings, etc. A few packages
> build things that are needed to complete the "make -n".
>
> + If no problem to that point, do a "make".
>
> In all cases, when something unexpected shows up, the README, INSTALL
> and similarly-named files are the place to go.
I did read both README and README.WIN, but didn't find anything in there
that seemed to relate. I didn't know about doc/INSTALL.
However, this looks like a good sequence to follow in the future.
Thanks!
-- Jeff
---------------------------------------------------------------
Keep away from people who try to belittle your ambitions.
Small people always do that, but the really great make you
feel that you, too, can become great. -- Samuel Clemens
---------------------------------------------------------------