nielsheyvaert at hotmail.com
Wed Feb 24 10:04:28 CET 2010
I've taken the monkey approach in trying to build the tool. Meaning: follow the instructions to the letter and see what happens.
In order for it to compile I had to include header files for the ar6000 module using the -I flag.
Turns out these headers are not included in the toolchain which you are instructed to install on the Wiki. These headers are part of the distro source tree. I don't have the SHR source tree on my system, only the AoF source tree. So I pointed the compiler to the header files under the AoF tree. It compiled with no issues.
If this is a prerequisite to have a source tree of a distro it should be mentioned on the Wiki page... don't you think? Unless I'm missing something.
What do you think?
> Date: Fri, 19 Feb 2010 14:17:45 +0200
> From: lvmtime at gmail.com
> To: devel at lists.openmoko.org
> Subject: Re: wmiconfig compilation
> Without knowing exactly what you did while tweaking the makefiles I
> can't be sure, but if the headers you were missing are part of the
> distribution you were building for (and not something to do with a
> specific hw module) then you may need to install the proper dev packages
> using opkg.
> I am not sure about other distros, but in Ubuntu this needs to be done
> from the actual root account and not via sudo (not sure why).
> The procedure is:
> . /usr/local/openmoko/arm/environment-setup # note this is a different
> script then the usual setupenv for compilation
> opkg-target pckage_im_missing-dev
> hope this helps.
> Niels Heyvaert wrote:
>> Hi list,
>> I hope this subject has not already been discussed (did not find it in the archives).
>> I've been trying to compile wmiconfig from source on a 64bit system after installing the toolchain as per the instructions on:
>> and downloading the source and modifying the path as per:
>> The make process panicked completely because of includes of header files that failed. By tweaking the Makefile I was able to compile without problems.
>> I had to add the path to the ar6000/include and ar6000/ar6000 directories to get it working.
>> Now my question is, does this mean my toolchain installation is incorrect?
>> Can be anything, I know, but given the fact that my system is quite fresh, I was wondering if something is missing in the documentation...
>> Any hints?
>> Thanks for your input,
Windows 7: helpt je meer voor elkaar te krijgen. Ontdek Windows 7.
More information about the devel