I disagree using bmake as default make
man src.conf
On Wed, May 22, 2013 at 9:01 PM, Julian Stecklina
jstec...@os.inf.tu-dresden.de wrote:
On 05/22/2013 01:05 PM, Julian Stecklina wrote:
This also affects building CURRENT from a 9.1 system. One workaround is
to build without -j, but
On 05/17/2013 09:45 PM, Florent Peterschmitt wrote:
Hi,
With the r250749 revision of head, rebuilt world with make -j4
buildworld, all was fine.
Then install new world, reboot and so:
$ cd /usr/src
$ make -j4 kernel
--- buildkernel ---
make: illegal option -- J
usage: make
On 05/22/2013 01:05 PM, Julian Stecklina wrote:
This also affects building CURRENT from a 9.1 system. One workaround is
to build without -j, but this is quite painful on an 8-core box.
I tried using bmake from ports, but this fails, because the build system
seems to have PATH hardcoded and
Le 20/05/2013 11:53, Boris Samorodov a écrit :
Seems to be a feature of the CURRENT build infrastructure.
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.
I managed to build/install world/kernel without
17.05.2013 23:45, Florent Peterschmitt пишет:
Hi,
With the r250749 revision of head, rebuilt world with make -j4
buildworld, all was fine.
Then install new world, reboot and so:
$ cd /usr/src
$ make -j4 kernel
--- buildkernel ---
make: illegal option -- J
usage: make
On Mon, May 20, 2013 at 01:53:28PM +0400, Boris Samorodov wrote:
17.05.2013 23:45, Florent Peterschmitt ??:
...
Then install new world, reboot and so:
$ cd /usr/src
$ make -j4 kernel
--- buildkernel ---
make: illegal option -- J
...
Can someone help ?
Seems to be a
Hi,
With the r250749 revision of head, rebuilt world with make -j4
buildworld, all was fine.
Then install new world, reboot and so:
$ cd /usr/src
$ make -j4 kernel
--- buildkernel ---
make: illegal option -- J
usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
[-d flags] [-E
