Dear Jeff,
in message [off-list ref] you wrote:
He's a mythological figure! I think he is really secretly several
people working as one incredible unit of productivity.
No, really, it's just me. And I'm still trying to figure out how the
clone() system call could be used for real-life applications :-)
never stopped me before! Basically, the answer is yes - at least I
have been using the ELDK with a linux-2.4.20 kernel (from kernel.org).
The key point to remember is that you should always compile user
applications against the Linux include files that glibc (and all the
rest of the target ELDK apps) are built against - Do NOT compile your
user applications against the newer Linux kernel.
10 of 10 points :-)
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Where shall I begin, please your Majesty?" he asked. "Begin at the
beginning," the King said, gravely, "and go on till you come to the
end: then stop." - Alice's Adventures in Wonderland, Lewis Carroll
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Wolfgang Denk wrote:
quoted
never stopped me before! Basically, the answer is yes - at least I
have been using the ELDK with a linux-2.4.20 kernel (from kernel.org).
The key point to remember is that you should always compile user
applications against the Linux include files that glibc (and all the
rest of the target ELDK apps) are built against - Do NOT compile your
user applications against the newer Linux kernel.
10 of 10 points :-)
Stupid question (TM):
If I'd built the ELDK from scratch and used Linux-2.4.20 include files
to build "glibc (and all the rest of the target ELDK apps)" I should
build my "applications against the newer Linux kernel"! Shouldn't I?
And in general: shouldn't I used a glibc that "matches" the kernel
version?
Thanks,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
10 of 10 points :-)
I'm on a role, so I'll try again against my better judgement.
Steven Scholz writes:
> If I'd built the ELDK from scratch and used Linux-2.4.20 include files
> to build "glibc (and all the rest of the target ELDK apps)" I should
> build my "applications against the newer Linux kernel"! Shouldn't I?
Yes, you are correct. The rule is to always build user space
applications against the same Linux include files that were used to
build glibc.
If, on the other hand, you are compiling a kernel module, then you
need to build it against the actual Linux kernel version you are
running.
>
> And in general: shouldn't I used a glibc that "matches" the kernel
> version?
I think that is the "safest" way of doing things, but apparently not
usually necessary. People upgrade their kernels all the time on their
native platforms without rebuilding their glibc. I believe some effort
is made to maintain binary compatiblity between glibc and the kernel -
but I'm sure it is not guaranteed.
Regards,
Jeff
--
Jeff Kowing [off-list ref]
All opinions expressed are my own and not of my employer.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/