On Wed, 2002-04-10 at 02:52, Wez Furlong wrote:
On 10/04/02, Stig S. Bakken [EMAIL PROTECTED] wrote:
m68k-linux-amiga it never dies, does it?
:-)
The trickiest part here seems to be detecting libc version on Linux. Or
is it enough to try reading symlinks in /lib?
You might
On Wed, 2002-04-10 at 00:22, Stig S. Bakken wrote:
The general format could be CPU-OS[-EXTRA]
I like OS-CPU[-EXTRA] more. A shell script (as one of your examples)
would often be CPU and EXTRA - but not OS - independend. If we use
OS-CPU[-EXTRA] it runs on eg. linux-*, and not *-linux*. It's not
Stig:
powerpc-macos-x Is there a need to distinguish between different
MacOS X revisions?
On the system level, we need to talk about Darwin. And the
version information is crucial, as the platform is evolving
rapidly.
So, for example:
powerpc-darwin-5.3
On 10/04/02, Stig S. Bakken [EMAIL PROTECTED] wrote:
I know, I am an old Atari TT owner. :-)
I have had linux/m68k running on amigas and a Sun 3/60 :-)
Personally, I would treat linux/m68k just like i386-linux, in terms of
which tests/checks you perform, except that it's m68k-linux
Hi,
I'm about to start adding support for platform-specific stuff in the
PEAR installer (prebuilt extensions, .bat/.cmd scripts for windows,
shell scripts for unix and so on). To do this I need a standard way of
describing the system PHP runs on. I guess the important bits of
information are:
On 10/04/02, Stig S. Bakken [EMAIL PROTECTED] wrote:
m68k-linux-amiga it never dies, does it?
:-)
The trickiest part here seems to be detecting libc version on Linux. Or
is it enough to try reading symlinks in /lib?
You might find that you need to do some glibc checks on m68k-linux
