On line use uname -m. This only gives you the "processor architecture"
(i386, i586, i686). -p returns unknown on my
machines, which I don't think is splendid, but I think I can guess
why its that way. In my laptop I've got an AMD of some sort, in my
desktops I've got varying Pentiums (pentii?...I forget my latin declensions,
and still think Intel should grow some nads and name
the next processor sextium....it will only be big news in America
somehow I suppose its probably difficult to map all the confusing
id names to human readable names..
A quick read of
/usr/src/linux/arch/i386/kernel/setup.c
seems to confirm this. I don't read much that would work on AMD or
Intel.
-Andy
-----Original Message-----
From: Pier P. Fumagalli <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, November 27, 2000 10:42 PM
Subject: Re: [Tomcat 4.0] SOLARIS-isms and other problems in native code
>Craig R. McClanahan <[EMAIL PROTECTED]> wrote:
>>
>> I'm trying to build the new native code stuff on my Linux box, and am
running
>> into the following SOLARIS-specific issues:
>>
>> service/src/native/jsvc.h
>> - The header file <sys/systeminfo.h> is SOLARIS specific
>>
>> service/src/native/jsvc_unix.c
>> - The sysinfo() system call, defined in <sys/systeminfo.h>
>> is SOLARIS specific
>
>Hmmm... Freak... I need sysinfo() to get the processor information. The VM
>library is linked at run-time using dl*() function, and it resides in
>/JAVA_HOME/lib/[processor]/libjvm.so
>Now, I need to resolve the [processor] name, and under Solaris the sysinfo
>call returns me that. Is there a way to find it out under Linux? I've also
>seen that the behaviour of "uname -p" (wich is the one that under Solaris
>returns i386/sparc) doesn't work under Linux (returns "unknown")... Is
there
>a way in wich I can possibly know what processor that machine is running in
>a portable way? Or do I have to start #ifdef ing???
>
>> connectors/src/
>> - No Makefile that copies Makedefs.orig to Makedefs
>>
>> connectors/src/webapplib/
>> - I can build the library, but what do I do with it?
>>
>> connectors/src/apache-1.3/
>> - How do I install and configure this connector in Apache?
>> (Among other things, it looks like it'll need access to the
>> "wa.h" header file at compile time, and the library
>> at runtime.)
>
>Ok... I'll take a look at the makefiles (I spent yesterday night trying to
>figure out a decent way to build sources, but... More on this later).
>The "webapplib" directory contains the actual "module" for an abstract web
>server. In the apache 1.3 directory there is just an adaptor between the
>webapp library and the web server... I'm writing some documentation on how
>that whole thing works...
>
> Pier
>
>--
>Pier P. Fumagalli Apache Software Foundation
<mailto:[EMAIL PROTECTED]>
>---------------------------------------------------------------------------
-
>Neque porro quisquam est qui dolorem ipsum quia dolor sit amet,
consectetur,
>adipisci velit... (Cicero: "De Finibus"
1.10.32)
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
