On Mon, Nov 25, 2013 at 03:57:53PM +0100, Marc Espie wrote:
> On Mon, Nov 25, 2013 at 12:14:04AM +0100, Juan Francisco Cantero Hurtado
> wrote:
> > The problem with some .xz files was the limited datasize of VAX (40MB).
> > miod@ increased the limits to 128MB with his last commits.
> >
> > OK?
>
> Okay for the patch.
>
> Your explanation of the problem is wrong, though. vax used to be our last
> gcc2 architecture, and gcc2 does not support one vital feature of C99, the
> ability to declare variables at another point besides the start of a block,
> which did kill xz very thoroughly.
I don't know what was the original problem but with VAX ported to gcc3
the remaining problem was the datasize because xz can use 65MB of RAM.
BTW, thanks for the compiler class :)
>
> >
> > Index: bsd.port.mk.5
> > ===================================================================
> > RCS file: /usr/cvsync/src/share/man/man5/bsd.port.mk.5,v
> > retrieving revision 1.386
> > diff -u -p -r1.386 bsd.port.mk.5
> > --- bsd.port.mk.5 7 Nov 2013 01:25:27 -0000 1.386
> > +++ bsd.port.mk.5 24 Nov 2013 22:56:21 -0000
> > @@ -1534,9 +1534,6 @@ do
> > gzip -dc ${FULLDISTDIR}/$$archive | tar xf -;;
> > esac
> > done
> > -.Ed
> > -The use of xz archives is discouraged, as it makes things impossible to
> > -build on vax.
> > .It Ev EXTRACT_ONLY
> > Set to the list of distfiles to actually extract if some distfiles
> > should not be extracted during the
>
--
Juan Francisco Cantero Hurtado http://juanfra.info
