hi all,
i'm porting the mali driver on the latest linux kernel. but it cannot work. firstly, i thought maybe i should check that the preprocessor output be the same under different linux kernel verison.
as gcc could use the -E options to get the preprocess output. after reading in the Document/kbuild/kbuild.txt, modules.txt. KCPPFLAGS=-E was set in the KDIR/Makefile, but the preprocessors output couldn't get in the *.o.
is that right? or is there any quick way to get the preprocessor output.
thanks a lot.
On 24/03/15 14:02, pleasurefish wrote:
hi all,
i'm porting the mali driver on the latest linux kernel. but it cannot work. firstly, i thought maybe i should check that the preprocessor output be the same under different linux kernel verison.
as gcc could use the -E options to get the preprocess output. after reading in the Document/kbuild/kbuild.txt, modules.txt. KCPPFLAGS=-E was set in the KDIR/Makefile, but the preprocessors output couldn't get in the *.o.
is that right? or is there any quick way to get the preprocessor output.
I do it the very dumb way!
I build with V=1 and then copy the resulting line, slap on a -E and run it outside of make.
Daniel.
would you pls tell me the details, :) At 2015-03-24 22:04:55, "Daniel Thompson" daniel.thompson@linaro.org wrote:
On 24/03/15 14:02, pleasurefish wrote:
hi all,
i'm porting the mali driver on the latest linux kernel. but it cannot work. firstly, i thought maybe i should check that the preprocessor output be the same under different linux kernel verison.
as gcc could use the -E options to get the preprocess output. after reading in the Document/kbuild/kbuild.txt, modules.txt. KCPPFLAGS=-E was set in the KDIR/Makefile, but the preprocessors output couldn't get in the *.o.
is that right? or is there any quick way to get the preprocessor output.
I do it the very dumb way!
I build with V=1 and then copy the resulting line, slap on a -E and run it outside of make.
Daniel.
On 24/03/15 15:13, pleasurefish wrote:
would you pls tell me the details, :)
You added V=1 to the kernel build flags which causes the build system to show the commands it is executing.
Then you find the specific command you want to see the pre-processed output for; copy it, add -E and run it by hand.
That's it!
Daniel.
At 2015-03-24 22:04:55, "Daniel Thompson" daniel.thompson@linaro.org wrote:
On 24/03/15 14:02, pleasurefish wrote:
hi all,
i'm porting the mali driver on the latest linux kernel. but it cannot work. firstly, i thought maybe i should check that the preprocessor output be the same under different linux kernel verison.
as gcc could use the -E options to get the preprocess output. after reading in the Document/kbuild/kbuild.txt, modules.txt. KCPPFLAGS=-E was set in the KDIR/Makefile, but the preprocessors output couldn't get in the *.o.
is that right? or is there any quick way to get the preprocessor output.
I do it the very dumb way!
I build with V=1 and then copy the resulting line, slap on a -E and run it outside of make.
Daniel.
Just run 'make path/file.i' On Mar 24, 2015 9:17 AM, "Daniel Thompson" daniel.thompson@linaro.org wrote:
On 24/03/15 15:13, pleasurefish wrote:
would you pls tell me the details, :)
You added V=1 to the kernel build flags which causes the build system to show the commands it is executing.
Then you find the specific command you want to see the pre-processed output for; copy it, add -E and run it by hand.
That's it!
Daniel.
At 2015-03-24 22:04:55, "Daniel Thompson" daniel.thompson@linaro.org
wrote:
On 24/03/15 14:02, pleasurefish wrote:
hi all,
i'm porting the mali driver on the latest linux kernel. but it cannot work. firstly, i thought maybe i should check that the preprocessor output be the same under different linux kernel verison.
as gcc could use the -E options to get the preprocess output. after reading in the Document/kbuild/kbuild.txt, modules.txt. KCPPFLAGS=-E was set in the KDIR/Makefile, but the preprocessors output couldn't get in the *.o.
is that right? or is there any quick way to get the preprocessor output.
I do it the very dumb way!
I build with V=1 and then copy the resulting line, slap on a -E and run it outside of make.
Daniel.
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
On 24/03/15 16:17, Tony Jones wrote:
Just run 'make path/file.i'
Awesome! I'll keep a note of that!
Daniel.
On Mar 24, 2015 9:17 AM, "Daniel Thompson" <daniel.thompson@linaro.org mailto:daniel.thompson@linaro.org> wrote:
On 24/03/15 15:13, pleasurefish wrote: would you pls tell me the details, :) You added V=1 to the kernel build flags which causes the build system to show the commands it is executing. Then you find the specific command you want to see the pre-processed output for; copy it, add -E and run it by hand. That's it! Daniel. At 2015-03-24 22:04:55, "Daniel Thompson" <daniel.thompson@linaro.org <mailto:daniel.thompson@linaro.org>> wrote: On 24/03/15 14:02, pleasurefish wrote: hi all, i'm porting the mali driver on the latest linux kernel. but it cannot work. firstly, i thought maybe i should check that the preprocessor output be the same under different linux kernel verison. as gcc could use the -E options to get the preprocess output. after reading in the Document/kbuild/kbuild.txt, modules.txt. KCPPFLAGS=-E was set in the KDIR/Makefile, but the preprocessors output couldn't get in the *.o. is that right? or is there any quick way to get the preprocessor output. I do it the very dumb way! I build with V=1 and then copy the resulting line, slap on a -E and run it outside of make. Daniel. _________________________________________________ linaro-android mailing list linaro-android@lists.linaro.__org <mailto:linaro-android@lists.linaro.org> http://lists.linaro.org/__mailman/listinfo/linaro-__android <http://lists.linaro.org/mailman/listinfo/linaro-android>
linaro-android@lists.linaro.org
-
Daniel Thompson -
pleasurefish -
Tony Jones