> On Thu, 16 Dec 1999, Jamie Lokier wrote:
>
> > Adam Heath wrote:
> > > -I$HOME/path/to/my/special/kernel/include
> >
> > And that path on a package I distribute that's compiled on /your/
> > machine is what, exactly?
>
> Use configure. Add a note to the readme(make KSRC=/path/to/foo/include).
>
> How often do you compile other programs and not have to modify some system
> dependant setting? Are you saying all systems are alike? Where's the fun in
> that?
IF you do user-mode programs which need access to linux-specific header
files you should use configure to test, whether the needed feature is in
the glibc linux/* headers, and if not you should use a version distributed
by _your_ software-package! I.e. you do the cp on your self, sort of a
linux_feature_cdrom_dosomeneatstuff_ioctl.h in your source-package.
With compiling kernel modules distributed seperately, one should go the
way MEC suggested some weeks ago (a directory in the kernel source,
where you can drop in the module source and use standard make configure &&
make modules).
Richard.
-- Richard Guenther <richard.guenther@student.uni-tuebingen.de> PGP: 2E829319 - 2F 83 FC 93 E9 E4 19 E2 93 7A 32 42 45 37 23 57 WWW: http://www.anatom.uni-tuebingen.de/~richi/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/