Re: Use of xmkmf
Re: Use of xmkmf
- Subject: Re: Use of xmkmf
- From: Joe Koski <email@hidden>
- Date: Fri, 28 Nov 2003 20:02:36 -0700
Is this the tip of the iceberg? As a recent convert to OS X (last May), and
a casual 10 year+ user of UNIX operating systems (mostly HP/UX), this may be
the time to comment. Fink not withstanding, I'm tired of OSF "make" files
and applications breaking on my Mac because of some arcane twist to the
Apple UNIX environment. I understand that every strain of UNIX is unique,
and that complete consistency is not in the interest of progress, but
shouldn't Apple try some of their jiggered gcc, etc. on some typical OSF
packages under typical use conditions? Maybe a key half dozen? At the least,
Apple should give advance feedback to OSF developers of the problems and how
to fix them; at most, they should reconfigure OS X to comply with the OSF
"standard." I realize that this applies mostly to the university and
scientific stuff that the typical Windows XP user doesn't really care about,
such as X11, Fortran, etc. How big is this engineering/scientific market for
Apple? With the G5 chip, I hope larger than they think.
Thanks, I do feel better already. As I was reminded last night, when I had
to switch back to OS 9 for one task, OS X is a considerable improvement. It
is also really good that Apple provides this forum.
Joe Koski
(a consultant who relies on economical scientific software for OS X)
on 11/28/03 4:27 PM, Sean Ahern at email@hidden wrote:
> Martin Costabel wrote:
>> The result is that more than 800 files in /usr/X11R6, scripts like
>> startx and xmkmf and all man pages, have an extra first line starting
>> with "#pragma GCC set_debug_pwd". In the case of the man pages this is
>> just ugly, but in the case of the scripts it is fatal, because the line
>> starting with "#!/bin/sh" works only when it is the first line, not when
>> it is the second line. Therefore these scripts are run not in /bin/sh as
>> they should, but in whatever shell is used to call them.
>>
>> The remedy is simple - just remove these first lines - so Apple (who
>> have known about this bug since before Panther hit the shelves) could
>> repair this for everybody easily with any software update. But since
>> this bug hits only geeks who run such scripts by hand from a non-default
>> shell, my guess is that they will not fix it anytime soon.
>
> This has been very annoying to me. I use cpp to process things which are
> not C/C++ files. Previous to Panther, I was able to use the -P flag,
> which is supposed to suppress these kind of things:
>
> -P Inhibit generation of linemarkers in the output from the
> preprocessor. This might be useful when running the preprocessor
> on something that is not C code, and will be sent to a program
> which might be confused by the linemarkers.
>
> Once I got to Panther, I always got that "#pragma" line at the top of the
> output, no matter what flags I passed to cpp. Annoying.
>
> -Sean
>
> __
> email@hidden
> 925-422-1648
> _______________________________________________
> x11-users mailing list | email@hidden
> Help/Unsubscribe/Archives:
> http://www.lists.apple.com/mailman/listinfo/x11-users
> X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html
> Report issues, request features, feedback:
> http://developer.apple.com/bugreporter
> Do not post admin requests to the list. They will be ignored.
_______________________________________________
x11-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/x11-users
X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html
Report issues, request features, feedback: http://developer.apple.com/bugreporter
Do not post admin requests to the list. They will be ignored.