Re: Building 4.x releases on 5.x and 6.x

From: Maxim Sobolev (sobomax_at_portaone.com)
Date: 12/30/04

  • Next message: Ruslan Ermilov: "Re: Building 4.x releases on 5.x and 6.x" 
    Date: Thu, 30 Dec 2004 01:17:41 +0200
To: Ruslan Ermilov <ru@FreeBSD.org>

    Ruslan Ermilov wrote:
    > On Thu, Dec 30, 2004 at 12:45:13AM +0200, Maxim Sobolev wrote:
    >
    >>Ruslan Ermilov wrote:
    >>
    >>>Hi Maxim,
    >>>
    >>>One thing you'll definitely need is to install the Perl port in
    >>>LOCAL_SCRIPT. Mounting /dev (much like the RELENG_5 and HEAD
    >>>versions of release/Makefile do) will also be needed. Note that
    >>>you should be using the 4.x version of release/Makefile* to
    >>>start "make release", and use WORLDDIR to point to your
    >>>/usr/src, something like this:
    >>>
    >>> cd /tmp
    >>> cvs co -rRELENG_4 -l release
    >>> cd /usr/src/release
    >>> make -f /tmp/Makefile release ...
    >>
    >>Do you mean that I need to have 5.x/6.x in /usr/src pointed to by
    >>WORLDDIR, while 4.x in /tmp/src and start making release in
    >>/tmp/src/release?
    >>
    >
    > I eman what I said: you need to use the target (4.x) version of
    > release/Makefile*, and /usr/src matching your running world and
    > kernel (5.x). WORLDDIR is not supported by 4.x release/Makefile,
    > hence the sequence above.
    >
    >
    >>I am not sure about perl, why do I need it? Isn't initial make
    >>buildworld expected to build it and install into pristive chroot'ed tree?
    >>
    >
    > You need Perl because 5.x doesn't have Perl in the base system,
    > hence initial "make installworld" (which will install 5.x world
    > into ${CHROOTDIR}) will not install Perl needed to build a 4.x
    > kernel.

    Maybe I am missing something obvious, but what if I'll build 4.x chroot
    on 5.x/6.x system, put 4.x sources into /usr/src and will try to build
    5.x release from within that chroot. As far as I can see, only
    operations that use some devices (e.g. md(4) vs vn(4)) can lead to a
    problem, but this . Anyway, pretty soon we will know for sure - it is
    now rolling distribution tarballs here.

    -Maxim
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Ruslan Ermilov: "Re: Building 4.x releases on 5.x and 6.x"

    Relevant Pages

    • Re: Building 4.x releases on 5.x and 6.x
      ... >> You need Perl because 5.x doesn't have Perl in the base system, ... >> kernel. ... > 5.x release from within that chroot. ...
      (freebsd-current)
    • Re: help with grep looking for cats and dogs
      ... >others would commonly do with perl one-liners. ... Actually perl is still in the base system. ... the perl scripts needed to install and/or compile and install ... I've had to go back to the base system for some ports when making ...
      (comp.unix.sco.misc)
    • Re: modify PVA.pl (z/OS and perl-5.8.6)
      ... This contains a sequence of property aliases ('ea' for EastAsianWidth, 'jt' for JoiningType and so on) and their corresponding values. ... I changed the order of propertynames in PVA_abbr_map, but perl -d still continues to follow the original sequence of property names and exits before 'ea' is used. ... I tried to modify PVA.pl manually on the linux box to to see if perl ran with this new sequence, so that the 'ea' case would be picked up before perl -d had a chance to exit. ...
      (perl.beginners)
    • Re: FAQ 5.2 (Was: inserting lines)
      ... I recently complained about the lack of alternate approaches to the FAQ ... "How do I change one line in a file/delete a line in a file/insert a ... Perl is not a text editor. ... punch cards--computers usually see the text file as a sequence of bytes. ...
      (comp.lang.perl.misc)
    • Re: Removing sequence tag from SOAP WSDL Schema -- help please
      ... "Marvin Smit" wrote: ... > used by a perl implementation, which uses hashes and therefore cannot ... > maintain a sequence?" ... just change the sequence information. ...
      (microsoft.public.dotnet.framework.webservices)