Date: Wed, 9 Oct 2013 17:56:02 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Anton Shterenlikht <mexas@bris.ac.uk> Cc: freebsd-ports@freebsd.org Subject: Re: poudriere: ELF binary type "0" not known. Message-ID: <20131009155602.GB95601@ithaqua.etoilebsd.net> In-Reply-To: <201310091548.r99FmJKh014284@mech-cluster241.men.bris.ac.uk> References: <20131009153617.GA95601@ithaqua.etoilebsd.net> <201310091548.r99FmJKh014284@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--Y7xTucakfITjPcLV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 09, 2013 at 04:48:19PM +0100, Anton Shterenlikht wrote: > >From baptiste.daroussin@gmail.com Wed Oct 9 16:42:02 2013 > >On Wed, Oct 09, 2013 at 04:06:42PM +0100, Anton Shterenlikht wrote: > >> I'm seeing this on the console: > >>=3D20 > >> load: 2.53 cmd: cc1 48388 [running] 2.92r 2.66u 0.04s 24% 35192k > >> sleep: about 1 second(s) left out of the original 2 > >> [ia64-default] [parallel_build:] [00/30] Built: 0 Failed: 0 Ignored= : 0=3D > > Skipped: 0 =3D20 > >> [01]: devel/qt4-corelib build (00:03:= 31) > >> [02]: lang/gcc build (00:03:= 31) > >> =3D3D=3D3D=3D3D=3D3D>> Logs: /pdr/data/logs/bulk/ia64-default/2013-10-= 09_14h59m33s > >> =3D3D=3D3D=3D3D=3D3D>> WWW: http://eis.bris.ac.uk/~mexas/poudriere/bul= k/ia64-defa=3D > >ult/2013-10-09_14h59m33s > >> =3D3D=3D3D=3D3D=3D3D>> [01] Finished build of devel/qt4-corelib: Succe= ss > >> =3D3D=3D3D=3D3D=3D3D>> [01] Starting build of x11-toolkits/qt4-gui > >> ELF binary type "0" not known. > >> ELF binary type "0" not known. > >> ELF binary type "0" not known. > >> ELF binary type "0" not known. > >> ELF binary type "0" not known. > >>=3D20 > >> Are the ELF error/warning messages being > >> emitted by the build failures? > >> Or are these issued by the poudriere itself? > > > >It is not issued by poudriere itself but by some failure, I have already= se=3D > >en a > >couple of them but I have never been able to figure out where they are f= rom, > >neither what impact it has, as it is not related to a failed port :(. >=20 > ok, thanks. > I was just thinking that all port build output > (stdout and stderr) are redirected to files, > so I shouldn't see anything at all related > to port build output on console. > Therefore this must be something else... All I know is that this problem should come because something is trying a l= inux binary which is not properly "brandelf"ed or something like this. regards, Bapt --Y7xTucakfITjPcLV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlJVfJEACgkQ8kTtMUmk6EzlkwCfW2s5bqb+/JiujV1uj//tWfTz QE0AmwbivKgjyEQTyeZFGJyG74krQcoF =Ibva -----END PGP SIGNATURE----- --Y7xTucakfITjPcLV--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131009155602.GB95601>