Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 May 2013 22:51:21 +0200
From:      Florent Peterschmitt <florent@peterschmitt.fr>
To:        freebsd-current@freebsd.org
Subject:   Re: [analyzed] bmake (installed as default make): make: illegal option -- J
Message-ID:  <519BDE49.50603@peterschmitt.fr>
In-Reply-To: <5199F298.5060608@passap.ru>
References:  <519688D6.4020309@peterschmitt.fr> <5199F298.5060608@passap.ru>

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

Le 20/05/2013 11:53, Boris Samorodov a =C3=A9crit :
>=20
> Seems to be a feature of the CURRENT build infrastructure.
>=20
> I have got almost two identical systems FreeBSD 10-amd64
> which I update several times a week. One is affected while
> the other is not.
>=20
> I managed to build/install world/kernel without '-j' option.
> But this did not help to recover '-j' option. Here is my further
> investigation.
>=20
> At the affected system I run "make -j 5" under ktrace. Here is the
> relevant part of kdump:
> -----
> [...]
>  38629 sh       CALL  read(0,0x624100,0x400)
>  38629 sh       GIO   fd 0 read 247 bytes
>        "{ cd /usr/src; PATH=3D/sbin:/bin:/usr/sbin:/usr/bin `if [ -x
> /usr/obj/usr/src/make.amd64/make ]; then echo /usr/obj/usr/src/make.a"
>  38629 sh       RET   read 247/0xf7
> [...]
>  38629 sh       CALL  wait4(0xffffffff,0x7fffffffd5f4,0<><invalid>0,0)
>  38631 sh       CALL  execve(0x801889778,0x8018898a0,0x8018898e8)
>  38631 sh       NAMI  "/usr/obj/usr/src/make.amd64/make"
>  38631 make     RET   execve 0
> [...]
>  38631 make     CALL  write(0x2,0x7fffffffbe80,0x1a)
>  38631 make     GIO   fd 2 wrote 26 bytes
>        "make: illegal option -- J
>        "
> [...]
> -----
>=20
> So, if there is a file /usr/obj/usr/src/make.amd64/make, it is
> launched. And if this make file is of the wrong version, it boils out.
>=20
> The affected system:
> -----
> % uname -a
> FreeBSD BB049.int.wart.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #24 r250806=
:
> Sun May 19 15:08:43 SAMT 2013
> bsam@BB049.int.wart.ru:/usr/obj/usr/src/sys/BB64X  amd64
>=20
> % LANG=3DC ls -l /usr/obj/usr/src/make.amd64
> total 1476
> -rwxr-xr-x  1 bsam  wheel  751094 May 17 14:52 bmake
> -rwxr-xr-x  1 bsam  wheel  686618 May 15 23:31 make
> drwxr-xr-x  3 bsam  wheel     512 Dec  9 12:19 usr
>=20
> % /usr/obj/usr/src/make.amd64/make -V MAKE_VERSION
> 10201205300
> -----
>=20
> Not affected system:
> -----
> % uname -a
> FreeBSD bsam.int.wart.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #22 r250806:=

> Sun May 19 22:07:39 SAMT 2013
> bsam@bsam.int.wart.ru:/usr/obj/usr/src/sys/BB64X  amd64
>=20
> % LANG=3DC ls -l /usr/obj/usr/src/make.amd64
> total 1543
> -rwxr-xr-x  1 bsam  wheel  751094 May 17 14:52 bmake
> -rwxr-xr-x  1 bsam  wheel  751060 May 19 16:31 make
> drwxr-xr-x  3 bsam  wheel       3 Jan  5 02:18 usr
>=20
> % /usr/obj/usr/src/make.amd64/make -V MAKE_VERSION
> 20130330
> -----
>=20
> So, the affected system has and uses the wrong version of
> /usr/obj/usr/src/make.amd64/make. And it even is not
> overritten while building (at least without -j option).
>=20
> Sure, if this file is removed, the whole status-quo is restored
> (i.e. the build with '-j' option proceeds).
>=20
> Well, where this behaviuor is expected or not remains a question
> I have no answer to.
>=20
You're right. I've juste rebuilt the world with previously rm -rf
/usr/obj/* to ensure anything could interfere with the new build.

I'll try soon with a partial rebuild and tell what's happening.

Thanks for investagation.

--=20
Florent Peterschmitt
+33 (0)6 64 33 97 92
florent@peterschmitt.fr

------------------------
O< ascii ribbon campaign
- stop html mail
- www.asciiribbon.org


------enig2LFTBEIGSUVOSBCHWLEWD
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.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRm95JAAoJEMtO2Sol0IIm3dEIAJ8zWpthTu5LIz8LqNLpGcGA
GgBgLrx7YnqFCD0NMz3khafD7sJIEWwJlPIgdNF9XFuGA8YkWm8Z3YMfH0Voqeac
KkPfFDQWaHtIUz2Vj8LC0366o9cYx/G+S89tCw9uCw1JKeZZMaGCY2YwJ/bBKKDR
Q8yUC1DafxtodXc1o97SJzp5xqTy8qWjdj4p0CYVGdKADhsngUwBkcX/yDQrdE/W
FgWeV42tFlO0xKgayLIxlZPRICnuiKfRSNHOXB2y5WXHEE94/F/YXcyM31dyy9KT
qp9ijz5E8vamwLSpfv3CITg+GN+nmUaKDYrR0xQh+B7TfpmZrCdMdJXXe3j5nHo=
=OHmN
-----END PGP SIGNATURE-----

------enig2LFTBEIGSUVOSBCHWLEWD--



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