Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Feb 2007 11:20:17 -0500
From:      Kris Kennaway <kris@obsecurity.org>
To:        LI Xin <delphij@delphij.net>
Cc:        Boris Samorodov <bsam@ipt.ru>, ports@FreeBSD.org, Gerald Pfeifer <gerald@pfeifer.com>, Kris Kennaway <kris@obsecurity.org>
Subject:   Re: make install: tar: could not chdir to '(null)'
Message-ID:  <20070205162016.GA87169@xor.obsecurity.org>
In-Reply-To: <45C6F065.5040206@delphij.net>
References:  <Pine.LNX.4.64.0702050034560.10525@acrux.dbai.tuwien.ac.at> <99933062@bs1.sp34.ru> <20070205014739.GA53389@xor.obsecurity.org> <45C6F065.5040206@delphij.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--7JfCtLOvnd9MIVvH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 05, 2007 at 04:52:53PM +0800, LI Xin wrote:
> Kris Kennaway wrote:
> > On Mon, Feb 05, 2007 at 03:12:41AM +0300, Boris Samorodov wrote:
> >> On Mon, 5 Feb 2007 00:38:54 +0100 (CET) Gerald Pfeifer wrote:
> >>
> >>> A few days ago, my FreeBSD 5.4-STABLE based tester (i386) started to =
fail=20
> >>> in building packages, most notably lang/gcc40, lang/gcc41 and above.
> >>>   % make install
> >>>   ldconfig: /files/pfeifer/porttest/gcc40/lib/gcc-4.0.4: ignoring dir=
ectory not owned by root
> >>>   ldconfig: mkstemp(/var/run/ld-elf.so.hints.iWE9fy): Permission deni=
ed
> >>>   % make package
> >>>   =3D=3D=3D>  Building package for gcc-4.0.4,1
> >>>   tar: could not chdir to '(null)'
> >>>   pkg_create: make_dist: tar command failed with code 256
> >>>   Creating package /sw/test/FreeBSD/ports/pcvs/gcc40/gcc-4.0.4,1.tbz
> >>>   Registering depends: ldconfig_compat-1.0_8 libiconv-1.9.2_2.
> >>>   Creating bzip'd tar ball in '/sw/test/FreeBSD/ports/pcvs/gcc40/gcc-=
4.0.4,1.tbz'
> >>>   *** Error code 1
> >>> Has any of you ever seen anything like this?  This also affects ports
> >>> which test just fine on other machines (6-CURRENT, for example) and
> >>> have been testing fine on this machine.
> >>> I tried to track this down, but failed so far.  From what I can tell,
> >>> there have been no changes on this machines which might trigger this.
> >> A CPU cooler full of dust / mulfunctionning?
> >=20
> > No :-) One of the changes in the last b.p.m patch presumably doesn't
> > work on FreeBSD <6.
>=20
> Does this mean that the ports tree is now officially removed 5.x
> support?  Does not sound like a good news... :-/

No, it means that our main testing target is 6.x, and sometimes there
will be unfortunate breakage localized on other branches.  When
someone can identify the cause of the problem we'll try and expedite a
fix or workaround.

Kris

--7JfCtLOvnd9MIVvH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFFx1lAWry0BWjoQKURArhzAKDdVv5FMDeBJhV6gX4+lnlMHF09wQCg2/3t
H7XztTNEI/aSh+YgalLVdVQ=
=EAyD
-----END PGP SIGNATURE-----

--7JfCtLOvnd9MIVvH--



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