Re: What should we do when headers are missing in 10.2?
Re: What should we do when headers are missing in 10.2?
- Subject: Re: What should we do when headers are missing in 10.2?
- From: Stéphane Sudre <email@hidden>
- Date: Wed, 11 Sep 2002 18:08:21 +0200
On Wednesday, September 11, 2002, at 05:30 PM, Jim Magee wrote:
On Wednesday, September 11, 2002, at 11:09 AM, Stiphane Sudre wrote:
In fact, my problem is not with the need to #include any file before
or after. The real issue is that the files are missing from
/usr/include in a complete Mac OS X 10.2 install (by complete, I mean
everything checked, last dev Tools, etc...).
Currently, I'm using the header files from a 10.1 backup but it's far
from being a good solution. So I'm asking for a
better/recommended/official solution.
It should be in /usr/include/netinet/ip_var.h. It should also be in
/System/Library/Frameworks/Kernel.framework/Headers/netinet/ip_var.h.
That's because you're building a kernel extension which cannot use the
headers in /usr/include.
Hum, it's not on mine. It's not on another machine with 10.2
This the content of /usr/include/netinet
Last login: Wed Sep 11 17:50:55 on ttyp2
Welcome to Darwin!
[coyotte:~] stephane% cd /usr/include/netinet
[coyotte:/usr/include/netinet] stephane% ls
bootp.h in.h ip6.h tcp.h tcp_timer.h
icmp6.h in_pcb.h ip_fw.h tcp_debug.h tcpip.h
if_ether.h in_systm.h ip_icmp.h tcp_fsm.h udp.h
igmp.h ip.h ip_mroute.h tcp_seq.h
[coyotte:/usr/include/netinet] stephane%
And it's not in the Kernel.framework either.
I installed 6C125 and 6C115. August Dev tools.
My 10.2 system, installed with only the contents of the released CDs
on a new volume, seems to have it. I remember there was a problem
with them being missing in earlier seeds of the developer tools, but I
thought for sure that was addressed. I'm sure someone more
knowledgeable than I will chime in with exactly which versions of
things have the fix.
If that's not your cup of tea (and it's certainly not the typical
business model of any long-time Mac developer), we are in the
process of creating a set of more sustainable APIs for such kernel
extensions. But as good as we are at guessing your needs, we aren't
psychic. You [all] need to let us know what services you need
sustainable interfaces for. Well do our best to include those [or
comparable equivalents].
This makes me think I'm currently wondering why memcmp is said not to
be defined when strings.h is included in a C source of a Kernel
extensions.
This is where that distinction between /usr/include and
Kernel.framework really kicks in. The kernel runtime environment is
[purposely] MUCH smaller than what you have available at user space.
As such, /System/Library/Frameworks/Kernel.framework/Headers/string.h
is NOT the identical file you have available at user space through
/usr/include/string.h. It is a greatly limited subset for what is
available in-kernel.
Ouch, I will investigate this.
Thanks for the info.
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.