richard offer wrote:
> What if your application contains some user code and a kernel module ?
> Want an obvious example ? X.
VMware is another. In such cases, they have to do the same as any other
system-specific packages: guess, or ask the user. Autoconf apps prefer
guessing; X uses Imake and
* $ from [EMAIL PROTECTED] at "10-Apr: 6:42pm" | sed "1,$s/^/* /"
*
*
* richard offer wrote:
* > * > uname does not always provide useful information (cross compiling).
Even
* > * > if you're building the same ISA, you maybe in a chroot'ed environment.
* > * >
* > * > Can we please not assume tha
richard offer wrote:
> * > uname does not always provide useful information (cross compiling). Even
> * > if you're building the same ISA, you maybe in a chroot'ed environment.
> * >
> * > Can we please not assume that everybody only ever builds native...
> *
> * Nobody is assuming that. If you'r
* $ from [EMAIL PROTECTED] at "10-Apr: 4:08pm" | sed "1,$s/^/* /"
*
*
* richard offer wrote:
* > uname does not always provide useful information (cross compiling). Even
* > if you're building the same ISA, you maybe in a chroot'ed environment.
* >
* > Can we please not assume that everybody only
richard offer wrote:
> uname does not always provide useful information (cross compiling). Even
> if you're building the same ISA, you maybe in a chroot'ed environment.
>
> Can we please not assume that everybody only ever builds native...
Nobody is assuming that. If you're hard enough to do a
In article <9aqmgo$8f6ol$[EMAIL PROTECTED]> you write:
>In article <[EMAIL PROTECTED]>,
>Marvin Stodolsky <[EMAIL PROTECTED]> wrote:
>>Thanks for responding. But I would still like to understand what the
>>functionality is of the build --> /usr/src/linuc. Is it dispensable,
>>once the module tr
Miquel van Smoorenburg wrote:
> >There is a way though I'd not call it clean. Here is an extract from
>
> Do you think something like this is the correct approach? If it
> was part of the official kernel you could write a Makefile like this:
>
> [code to creake /lib/modules/`uname -r`/config.mak
In article <[EMAIL PROTECTED]>,
Jamie Lokier <[EMAIL PROTECTED]> wrote:
>Miquel van Smoorenburg wrote:
>> .. but there should be a cleaner way to get at the CFLAGS used
>> to compile the kernel.
>
>There is a way though I'd not call it clean. Here is an extract from
Do you think something like
Miquel van Smoorenburg wrote:
> .. but there should be a cleaner way to get at the CFLAGS used
> to compile the kernel.
There is a way though I'd not call it clean. Here is an extract from
the Makefile I am using for separately-distributed modules. It should
work with kernels 2.0 to 2.4, all su
In article <[EMAIL PROTECTED]>,
Marvin Stodolsky <[EMAIL PROTECTED]> wrote:
>Thanks for responding. But I would still like to understand what the
>functionality is of the build --> /usr/src/linuc. Is it dispensable,
>once the module tree has been installed?
It's needed for modules that are di
Russell
Thanks for responding. But I would still like to understand what the
functionality is of the build --> /usr/src/linuc. Is it dispensable,
once the module tree has been installed?
Incidentally, per below, my own modutils is current, though some of the
folks using our ltmodem.o compiler
On Sun, Apr 08, 2001 at 09:47:06AM -0500, Marvin Stodolsky wrote:
> It's presence has required some gymnastics, per below, during module
> installation for the Winmodem driver, ltmodem.o requiring a subsequent
> "depmod -a"
You need to update your modutils package - there have been a number of
im
the
2.4.nn ??:
# ls -l /lib/modules/2.4.3/
total 24
lrwxrwxrwx1 root root ??? 20 Apr 2 17:00 build ->
/usr/src/linux-2.4.3
drwxr-xr-x6 root root 1024 Apr 2 17:00 kernel
-rw-r--r--1 root root 4725 Apr 8 08:06 modules.dep
-rw-r--r--1
13 matches
Mail list logo
