It sounds like you're seeing something similar to what I've had once in
a while, where a package just won't build no matter what.
I've never discovered the root cause, so I'm not sure if we're having
the same problem, but in the past I have succeeded in making things
build by deleting the "tmp" directory inside my "overo-oe" directory.
This might be a bit brutal, as a lot of source will need to be
re-downloaded. But my internet connection is decent, so it hasn't slowed
me down too much, yet.
Before killing your entire "tmp" directory, it might be worth a shot to
see if deleting just the
will make it work. Somebody with more intimate knowledge will probably
correct me, but I suspect that sometimes the source code does not
download and/or uncompress properly, which results in these funny errors
that aren't fixed by simply cleaning and rebuilding a package.
On 07/28/2010 14:35, AJ ONeal wrote:
> I've been banging my head against this one for a while now.
> I've tried cleaning, I've tried re-downloading the source.
> I just can't get past this and I would greatly appreciate some help.
> Again, this is with a fresh install of overo-oe.
> ERROR: log data follows
> | NOTE: make
> | mkdir objects
> | CC="arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8
> -mfpu=neon -mfloat-abi=softfp -Iproto -DHAVE_CONFIG_H
> *| sh:
> No such file or directory*
> | make: *** [auto/osdef.h] Error 127
> | FATAL: oe_runmake failed
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> gumstix-users mailing list