Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 May 2007 23:20:04 +0800
From:      LI Xin <delphij@delphij.net>
To:        Giorgos Keramidas <keramida@ceid.upatras.gr>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: RELENG_6_2 broken on latest -HEAD
Message-ID:  <4655AD24.5000805@delphij.net>
In-Reply-To: <20070524132352.GC2803@kobe.laptop>
References:  <46554442.7070502@delphij.net> <20070524132352.GC2803@kobe.laptop>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB48050003C9CE97F8380C2F4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Giorgos Keramidas wrote:
> On 2007-05-24 15:52, LI Xin <delphij@delphij.net> wrote:
>> Hi,
>> It seems that we can not build RELENG_6_2 world with -HEAD userland
>> anymore, after the gcc upgrade.  So the only way to build RELENG_6_2
>> releases is to create a chroot environment for now?
>=20
> I think this was never really ``supported''.  It may work, but if it
> breaks nobody is going to fix it.
>=20
> What *is* supported and should always work is building CURRENT on the
> latest RELENG_X branch.  But what you are doing is the reverse...

Okay, I just thought that using chroot to build release is a bit weird :-=
)

As a side note, my real concern is that, it seems that our build
infrastructure can not bootstrap itself very easily, say it's not "that"
self-contained as I imagined.  After installing a gcc 3.4.6 from ports
collection and override CC/CXX variables, I found that some of the
installed headers and bsd.*.mk is still used during the build, making it
very hard to produce successful build without heavy hack to the source
tree.  I think it's time for me to pursue more about our build skeleton..=
=2E

Cheers,
--=20
Xin LI <delphij@delphij.net>	http://www.delphij.net/
FreeBSD - The Power to Serve!


--------------enigB48050003C9CE97F8380C2F4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGVa0kOfuToMruuMARCsosAJwIUjSsU3KTv4r10j+h5wMS9CG1OQCfapaz
1df6KIySew4Ps0HTt2EpSiI=
=lZ+1
-----END PGP SIGNATURE-----

--------------enigB48050003C9CE97F8380C2F4--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4655AD24.5000805>