/usr/include/machine/cpu.h (like that?)

1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

Post #73,568 by boxley 1/8/03 11:17:19 PM Reply	/usr/include/machine/cpu.h (like that?) will work for cash and other incentives [link\|http://home.tampabay.rr.com/boxley/resume/Resume.html\|skill set] You think that you can trust the government to look after your rights? ask an Indian
Post #73,570 by admin 1/8/03 11:21:24 PM Reply	Doesn't exist on this box. Or were you just giving an example of what you thought I was looking for? Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #73,571 by boxley 1/8/03 11:27:50 PM Reply	osx has 3 entries /usr/include/machine/cpu.h * @APPLE_LICENSE_HEADER_END@ / #ifndef _BSD_MACHINE_CPU_H_ #define _BSD_MACHINE_CPU_H_ #if defined (__ppc__) #include "ppc/cpu.h" #elif defined (__i386__) #include "i386/cpu.h" #else #error architecture not supported #endif #endif / _BSD_MACHINE_CPU_H_ / as you can see it is a stub so you might be able to write one out and add it to the build. /usr/include/i386/cpu.h @APPLE_LICENSE_HEADER_END@ / / * HISTORY * / #ifndef _BSD_I386_CPU_H_ #define _BSD_I386_CPU_H_ #include <sys/appleapiopts.h> #ifdef __APPLE_API_OBSOLETE #define cpu_number() (0) #endif / __APPLE_API_OBSOLETE / #endif / _BSD_I386_CPU_H_ */ hope anything helps, you might want to write one thanx, bill will work for cash and other incentives [link\|http://home.tampabay.rr.com/boxley/resume/Resume.html\|skill set] You think that you can trust the government to look after your rights? ask an Indian
Post #73,573 by admin 1/8/03 11:39:26 PM Reply	Heh. No /usr/include/i386 either. But yes, that's the sort of thing I'm looking for. Thanks. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."

Determining platform type/OS in gcc via #defines - (admin) - (25) - Jan. 8, 2003, 07:48:54 PM EST

Maybe Mozilla source would help... - (Another Scott) - (1) - Jan. 8, 2003, 08:26:13 PM EST

Yes, this is the sort of thing I was looking for: - (admin) - Jan. 8, 2003, 09:34:57 PM EST

Is this on Linux? - (deSitter) - (8) - Jan. 8, 2003, 08:35:32 PM EST

what he said -NT - (boxley) - Jan. 8, 2003, 08:54:28 PM EST

I wasn't clear enough. - (admin) - (6) - Jan. 8, 2003, 09:33:28 PM EST

Gotta be a #pragma right? - (deSitter) - (1) - Jan. 8, 2003, 09:59:56 PM EST

#define -NT - (admin) - Jan. 8, 2003, 10:03:15 PM EST

/usr/include/machine/cpu.h (like that?) -NT - (boxley) - (3) - Jan. 8, 2003, 11:17:19 PM EST

Doesn't exist on this box. - (admin) - (2) - Jan. 8, 2003, 11:21:24 PM EST

osx has 3 entries - (boxley) - (1) - Jan. 8, 2003, 11:27:50 PM EST

Heh. No /usr/include/i386 either. - (admin) - Jan. 8, 2003, 11:39:26 PM EST

I don't really have an answer handy... - (ChrisR) - (13) - Jan. 8, 2003, 09:24:43 PM EST

Compile time, without passing -D switches. -NT - (admin) - (12) - Jan. 8, 2003, 09:35:48 PM EST

If memory serves me correct... - (ChrisR) - (11) - Jan. 8, 2003, 09:41:52 PM EST

Right. But I don't want to pass -D switches. :-) - (admin) - (10) - Jan. 8, 2003, 09:53:26 PM EST

Could autoconf help? - (static) - (9) - Jan. 9, 2003, 04:14:56 AM EST

We have our own build system; autoconf not a part of it -NT - (admin) - (8) - Jan. 9, 2003, 08:19:36 AM EST

Autoconf could still be useful - (neelk) - (7) - Jan. 9, 2003, 01:24:15 PM EST

Autoconf does so at runtime. - (admin) - (6) - Jan. 9, 2003, 01:34:45 PM EST

Are we talking about "configure" script? - (Arkadiy) - (5) - Jan. 9, 2003, 03:42:14 PM EST

You misunderstand me. - (admin) - (4) - Jan. 9, 2003, 03:46:40 PM EST

One man's compile time... - (ChrisR) - (3) - Jan. 9, 2003, 04:04:20 PM EST

I already do that; I don't want to. :-) - (admin) - (2) - Jan. 9, 2003, 04:38:25 PM EST

So what you're really wanting is... - (ChrisR) - (1) - Jan. 9, 2003, 04:46:21 PM EST

s/wanting/using - (admin) - Jan. 9, 2003, 05:01:51 PM EST

iwethey.org

We've spent the past two years building up an immunity to Iocaine!
188 ms