Christian Gieseler
2013-01-08 15:06:53 UTC
Hi all,
I am migrating a sentec cobra based board with mcf5329 from linux 2.6.25 to
linux 3.6.
After setting up the configuration I have some issues with the include
directories.
<stdin>:1:24: error: asm/unistd.h: No such file or directory
<stdin>:1:24: error: asm/unistd.h: No such file or directory
The headers are not found. A similar issue has been described here:
http://mailman.uclinux.org/pipermail/uclinux-dev/2010-March/050157.html
if I change the include directory in the uClibc configuration to the new
location
of the asm directory " linux/limits.h and friends" are missing, which are
still in the old location.
So at some point I have to do some changes to make the configuration work.
In the link posted above Greg said the following:
" But... All this is done automatically in the normal build flow
of the uClinux-dist. You shouldn't need to be doing any of
this manually."
Am I missing a configuration option that has to be changed? If a link is
the way to go, what
is the best way/file to do this? Do it manually or integrate the creation of
the link in the build
process. Which file should be used then?
Thank you for any feedback.
Regards
Christian
I am migrating a sentec cobra based board with mcf5329 from linux 2.6.25 to
linux 3.6.
After setting up the configuration I have some issues with the include
directories.
<stdin>:1:24: error: asm/unistd.h: No such file or directory
<stdin>:1:24: error: asm/unistd.h: No such file or directory
The headers are not found. A similar issue has been described here:
http://mailman.uclinux.org/pipermail/uclinux-dev/2010-March/050157.html
if I change the include directory in the uClibc configuration to the new
location
of the asm directory " linux/limits.h and friends" are missing, which are
still in the old location.
So at some point I have to do some changes to make the configuration work.
In the link posted above Greg said the following:
" But... All this is done automatically in the normal build flow
of the uClinux-dist. You shouldn't need to be doing any of
this manually."
Am I missing a configuration option that has to be changed? If a link is
the way to go, what
is the best way/file to do this? Do it manually or integrate the creation of
the link in the build
process. Which file should be used then?
Thank you for any feedback.
Regards
Christian