On Sun, 26 Oct 1997, Scott Ellis wrote:
> On Sun, 26 Oct 1997, Paul Miller wrote:
>
> > > For the most part, everything is compiled only for hamm. Many (most?)
> > > developers don't have access to machines for compiling libc5-based stuff
> > > easily anymore, and bo is supposed to be frozen exc
On Sun, 26 Oct 1997, Scott Ellis wrote:
> On Sat, 25 Oct 1997, Paul Miller wrote:
>
> > When a new version of a program is released, is a copy compiled to bo and
> > another for hamm? .. or is bo left without any updates? The reason I ask
> > is I thinking of re-installing the bo distribution be
On Sun, 26 Oct 1997, Paul Miller wrote:
> > For the most part, everything is compiled only for hamm. Many (most?)
> > developers don't have access to machines for compiling libc5-based stuff
> > easily anymore, and bo is supposed to be frozen except for security and
> > severe bugfix releases.
>
On Sun, 26 Oct 1997, Scott Ellis wrote:
> On Sat, 25 Oct 1997, Paul Miller wrote:
>
> > When a new version of a program is released, is a copy compiled to bo and
> > another for hamm? .. or is bo left without any updates? The reason I ask
> > is I thinking of re-installing the bo distribution be
On Sat, 25 Oct 1997, Paul Miller wrote:
> When a new version of a program is released, is a copy compiled to bo and
> another for hamm? .. or is bo left without any updates? The reason I ask
> is I thinking of re-installing the bo distribution because I can barely
> compile anything using hamm. -
When a new version of a program is released, is a copy compiled to bo and
another for hamm? .. or is bo left without any updates? The reason I ask
is I thinking of re-installing the bo distribution because I can barely
compile anything using hamm. -- probably libc6 releated, but it still
doesn't w
6 matches
Mail list logo
