Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
> Because sh5, as indicated by its name, is the System V shell. It will
> not be found on a pure BSD system. Similarly, ksh, the Korn shell, is
> a Bell Labs invention made well after the BSD split.
>
> Systems like Ultrix have sh5 because, although t
Mo McKinlay <[EMAIL PROTECTED]> wrote:
> Actually, what I find more amusing is the fact that BSD is a free
> replacement for UNIX. Which is exactly what the GNU project aims for,
> albeit with different licensing terms. I fail to see how BSD *can* be
> "pure UNIX", when "pure UNIX" is exactly wha
Akim Demaille, who I gather is the autoconf maintainer (please correct me if
I'm wrong), has stated on the gcc mailing list, which I subscribe to, that he
didn't know much about traditional and pure UNIX systems (traditional and pure
for me, for you I guess ancient and broken) and wanted to learn
"John A. Crow" <[EMAIL PROTECTED]> writes:
> I would like to know what is the standard or preferred way of setting
> a variable at the configure command line.
In the CVS version of autconf you can do:
configure MYVAR="value of myvar"
In autoconf 2.13, you have to do:
env MYVAR="value of myvar"
> Absolutely right! You got it!
>
> System V and Pure BSD are just like the USA and USSR during the Cold War. We,
Last time I checked, the Cold War was kinda over ...
> the Pure BSD camp, will never have anything from Missed'em-five. That's why we
> are *pure* BSD. Being SysVile-free is what
Assar Westerlund writes:
> Lars Hecking <[EMAIL PROTECTED]> writes:
> > > env MYVAR="value of myvar" configure
> >
> > That's C shell syntax, which is quite limited.
>
> Not really. I used env to make the example shell-independent. You
> can have any number of variable assignments with env.
Donn Terry <[EMAIL PROTECTED]> wrote:
> Sort of as a poll: on what systems is the getconf
> command not present [...]
4.3BSD.
--
Michael Sokolov Harhan Engineering Laboratory
Public Service AgentInternational Free Computing Task Force
International Engineerin
Alex Hornby <[EMAIL PROTECTED]> wrote:
> Does anyone have a pure 4.3BSD system connected up to the net?
I do, of course, and not just one machine but a full machine room of them.
Absolutely pure in every way: I have my own classful net (class C, but still a
real full C, not a /24 chunk of someon
--
Hello -
I would like to know what is the standard or preferred way of setting
a variable at the configure command line. What I am hoping is there
is some way to do something like
% configure --set MYVAR="value of myvar"
An AC_SUBST(MYVAR) call then could be used to force the substituti
Assar Westerlund writes:
> "John A. Crow" <[EMAIL PROTECTED]> writes:
> > I would like to know what is the standard or preferred way of setting
> > a variable at the configure command line.
>
> In the CVS version of autconf you can do:
>
> configure MYVAR="value of myvar"
>
> In autoconf 2.13,
Lars Hecking <[EMAIL PROTECTED]> writes:
> > env MYVAR="value of myvar" configure
>
> That's C shell syntax, which is quite limited.
Not really. I used env to make the example shell-independent. You
can have any number of variable assignments with env.
/assar
11 matches
Mail list logo
