Getting # Physical CPUs

[Steven Schveighoffer]

On Thu, 15 Jul 2010 14:40:57 -0400, Walter Bright  
<newshound2 at digitalmars.com> wrote:

> dsimcha wrote:
>> Here's the error message I'm getting.  I know basically nothing about  
>> make except
>> that it's a build system and that it almost never works, so I can't  
>> even begin to
>> debug this.  Here's the error message I've been getting, on a freshly  
>> unpacked
>> 2.047 directory on some ancient  Linux distro that my sys admin insists  
>> on using:
>>  $ make -flinux.mak
>> make --no-print-directory -f  OS=posix BUILD=release
>> make[1]: OS=posix: No such file or directory
>> make[1]: *** No rule to make target `OS=posix'.  Stop.
>> make: *** [release] Error 2
>
> The "OS=posix" sets the macro OS to the value posix, it does not set the  
> target. This has been a feature of make since at least the 1980's,  
> earlier than Linux even existed. So I'm astonished you're seeing this  
> error.

The issue is the -f is passed a blank argument.  Probably in linux.mak,  
it's calling something like this:

make --no-print-directory -f $(SUB_MAKE_FILE) OS=$(OS) BUILD=release

or something like that, and SUB_MAKE_FILE isn't being set for some reason.

I think make is interpreting that OS=posix as a makefile to use.

-Steve