Summary:ASTERISK-01687: main Makefile doesn't work with MacOS 10.2
Reporter:lwc (lwc)Labels:
Date Opened:2004-05-24 15:26:05Date Closed:2004-09-25 02:45:05
Versions:Frequency of
Description:Makefile in main directory checks for version 7.0.0 result from uname -r
(line 167). Current version of MacOS (10.3.3) returns 7.3.0.
I hate to say this but each version of MacOS seems to change this response - Panther (10.3) returned 7.2.0; Jaguar (10.2) returned 7.0.0 if I recall, and the current version is 7.3.0. Sigh.


Sorry for waiting so long - it's one of the things I do whenever I get a full CVS load. This time I remembered to report it.
Comments:By: lwc (lwc) 2004-05-24 15:41:24

Correction - it does work for 10.2 - it doesn't work for MacOS X versions not equal to 10.2. - web report interface seems to have lost the .NE.

By: Mark Spencer (markster) 2004-05-24 17:08:18

Recommended fix?

By: lwc (lwc) 2004-05-24 19:04:46

Very good question. Recommended hack at end.

BTW, in a month a preview of the next version of MacOS X will appear. Given our luck, this will change the uname -r result again. I'll report if it does (ADC member :).

I don't know of any way to do a partial string match in make.
Ideally, one would check for the substring "7." , and any mid/minor version will do.

It was intended only to ensure that folk have MacOS 10.2 or above (i.e. uname -r reports "7.x.0"), as that brought in some better BSD support - as we now have to have some infeasably new version of Bison, this is a moot point.

Recommended fix:
I'm not at all sure that there are many 10.x (where x < 2) setups left, so it's
tempting to ->comment out<- the whole uname -r check. Ugly, but it works.

By: Mark Spencer (markster) 2004-05-24 22:37:49

Done, just as you suggested.