[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ranlib question
From: |
J.J. Merelo Guervos |
Subject: |
Re: ranlib question |
Date: |
Tue, 19 Dec 95 09:36:04 +0100 |
>>>>> "Nelson" == Nelson Minar <address@hidden> writes:
Hi:
Nelson> Just curious - are SysV people without ranlib finding the
Nelson> RANLIB variable in Makefile.conf a suitable way to
Nelson> configure things? Does /bin/true ignore its arguments on
Nelson> SysV? I sure hope so!
Actually, I don't use it. The makefile tries to run it, finds an
error, and goes on, since there is a dash at the beginning of the
line. What autoconf would do here is to set RANLIB to ":"; the
Makefile should check for that.
Nelson> eventually so you don't have to edit anything by hand, but
Nelson> autoconf isn't very good at finding some of the libraries
Nelson> we need. Also, autoconf's real strength is in fixing
Theoretically, it should find anything. It's pretty good now (2.7), just
running autoscan creates a configure.in skeleton that you can fill in.
Nelson> incompatibilities between various versions of libc, but
Nelson> we're mostly aiming for portability that doesn't require
Nelson> ifdefs for special OS versions.
As soon as you don't need to interact with the system too much, you
can... but if you need to send signals, for instance, all
compatibility goes to hell and beyond.
See ya
JJ
- ranlib question, Nelson Minar, 1995/12/19
- Re: ranlib question,
J.J. Merelo Guervos <=