Re: Wiki outdated ? was Re: Problems building ASU image

[Didier "Ptitjes"]

Didier "Ptitjes" wrote:
> Rod Whitby wrote:
>> Didier "Ptitjes" wrote:
>>> It seems that the Wiki is outdated.
>> Please update the wiki to match reality.
> 
> I'll do it.

You've done it better than I could have done!

Cheers, Didier

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wiki outdated ? was Re: Problems building ASU image

[Didier "Ptitjes"]

Believe me or not: A fresh new Makefile in a correct ~moko home.

$ make setup
$ make setup-machine-freerunner

Edit build/conf/local.conf

MACHINE = "x86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
TARGET_FPU = ""

$ make image

does the unable to open local.conf error.

Add INHERIT += " rm_work" and this will work. As I don't yet understand 
all of the toolchain and building process, I can't explain why!

I can't show now as I added the INHERIT += " rm_work" and I'm building 
an image.

Best regards, Didier.

Rod Whitby wrote:
> Didier "Ptitjes" wrote:
>> I just noticed that this behavior only occurs when building for the 
>> "x86" machine. I say this if this can help to identify the problem.
> 
> Do you mean x86 as a host, or x86 as a target.  x86 as a target is not
> supported, and x86 as a host is what everyone uses, so you can assume that
> that works.
> 
>> BTW the makefile process is great. I used Gentoo daily so I like it. I 
>> would suggest to add a "x/n" numbering for packages selected to be 
>> build, as does emerge.
> 
> MokoMakefile just sets up an environment and then calls bitbake.  Numbering
> of packages selected to be built is the domain of bitbake.
> 
> -- Rod
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
> 
> 

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wiki outdated ? was Re: Problems building ASU image

[Rod Whitby]

Didier "Ptitjes" wrote:
> I just noticed that this behavior only occurs when building for the 
> "x86" machine. I say this if this can help to identify the problem.

Do you mean x86 as a host, or x86 as a target.  x86 as a target is not
supported, and x86 as a host is what everyone uses, so you can assume that
that works.

> BTW the makefile process is great. I used Gentoo daily so I like it. I 
> would suggest to add a "x/n" numbering for packages selected to be 
> build, as does emerge.

MokoMakefile just sets up an environment and then calls bitbake.  Numbering
of packages selected to be built is the domain of bitbake.

-- Rod

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wiki outdated ? was Re: Problems building ASU image

[Didier "Ptitjes"]

Rod Whitby wrote:
> Didier "Ptitjes" wrote:
>> It seems that the Wiki is outdated.
> Please update the wiki to match reality.

I'll do it.

>> I'm wondering if anyone has done a fresh build restarting from scratch 
>> with the MokoMakefile as I can't explain my problems.
> 
> Yes.  Make sure you always "make clobber" if you move the build directory.

I tried to do make clobber (even if I did not move the build 
directory...) but this did not help.

I just noticed that this behavior only occurs when building for the 
"x86" machine. I say this if this can help to identify the problem.

BTW the makefile process is great. I used Gentoo daily so I like it. I 
would suggest to add a "x/n" numbering for packages selected to be 
build, as does emerge.

Best regards, Didier.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wiki outdated ? was Re: Problems building ASU image

[Rod Whitby]

Didier "Ptitjes" wrote:
> It seems that the Wiki is outdated.

Yes, wiki's are always outdated. :-(

> For example, the Wiki says you have 
> to make openmoko-devel-image or openmoko-qtopia-x11-image. But the 
> MokoMakefile version I downloaded has no such target but you have to set
> 
>   OM_IMAGE_NAME := openmoko-asu-image
> 
> in the Makefile and make image.

Please update the wiki to match reality.

> I'm wondering if anyone has done a fresh build restarting from scratch 
> with the MokoMakefile as I can't explain my problems.

Yes.  Make sure you always "make clobber" if you move the build directory.

-- Rod

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wiki outdated ? was Re: Problems building ASU image

[Rod Whitby]

Didier "Ptitjes" wrote:
> OK I found the problem finaly.
> 
> The Wiki states what follows for the local.conf :
> 
> MACHINE = "x86"
> DISTRO = "openmoko"
> BUILD_ARCH = "i686"
> INHERIT += " devshell"
> TARGET_FPU = ""
> 
> but the INHERIT += " rm_work" is mandatory else the bitbake doesn't work 
> at all as you can see in the errors of my previous message.

rm_work should have no effect on whether bitbake can find configuration
files.  Are you sure it wasn't some other change you made?

Someone else had the same problem as you when they moved the build directory
and did not do a "make clobber" between moving the directory and starting a
new build ...

-- Rod

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Wiki outdated ? was Re: Problems building ASU image

[Didier "Ptitjes"]

OK I found the problem finaly.

The Wiki states what follows for the local.conf :

MACHINE = "x86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
TARGET_FPU = ""

but the INHERIT += " rm_work" is mandatory else the bitbake doesn't work 
at all as you can see in the errors of my previous message.

Thanks anyway. Didier.

Didier "Ptitjes" wrote:
> Hello,
> 
> It seems that the Wiki is outdated. For example, the Wiki says you have 
> to make openmoko-devel-image or openmoko-qtopia-x11-image. But the 
> MokoMakefile version I downloaded has no such target but you have to set
> 
>   OM_IMAGE_NAME := openmoko-asu-image
> 
> in the Makefile and make image.
> 
> I'm wondering if anyone has done a fresh build restarting from scratch 
> with the MokoMakefile as I can't explain my problems.
> 
> This is really annoying. I'm blocked before anything may even be compiled!!
> 
> Please help. Didier.
> 
> Didier "Ptitjes" wrote:
>> But if you look at the log it can read the conf files!
>> Anyway, I've got rw on all my files...
>>
>> Didier.
>>
>> Davide Scaini wrote:
>>> permissions??? maybe it's really silly...
>>> d
>>>
>>> On Fri, Sep 12, 2008 at 1:44 PM, Didier Ptitjes <[EMAIL PROTECTED] 
>>> > wrote:
>>>
>>>
>>> Hello,
>>>
>>> Sorry this may be a dumb question. I'm trying to build an ASU image for
>>> x86 with the MokoMakefile for several days without success.
>>>
>>> I carefully followed the explanations of Wiki, searched the
>>> mailling-lists and the Web for a tip, but I always get the same error
>>> message.
>>>
>>> [EMAIL PROTECTED] ~ $ make image
>>> ( cd build && . ../setup-env && \
>>>  ( bitbake openmoko-asu-image u-boot-openmoko ) )
>>> ERROR: Unable to open conf/bitbake.conf
>>>
>>> I checked my setup-env file. All this seems correct. I also echoed
>>> BBPATH from it and it seems correct too.
>>>
>>> I added -DDD to the bitbake command in the Makefile and it looks like it
>>> opens the conf file and process it but then it stops with the same
>>> message...
>>>
>>> I can't understand why!
>>>
>>> Thanks for your help. Didier.
>>>
>>> Output with -DDD :
>>>
>>> [EMAIL PROTECTED] ~ $ make image
>>> ( cd build && . ../setup-env && \
>>>  ( bitbake -DDD openmoko-asu-image u-boot-openmoko ) )
>>> DEBUG: CONF reading /home/moko/openembedded/conf/bitbake.conf
>>> DEBUG: update_data()
>>> DEBUG: update_data()
>>> DEBUG: CONF conf/bitbake.conf:539: including conf/site.conf
>>> DEBUG: CONF including /home/moko/build/conf/site.conf
>>> DEBUG: update_data()
>>> DEBUG: CONF conf/bitbake.conf:540: including conf/auto.conf
>>> DEBUG: CONF file 'conf/auto.conf' not found
>>> DEBUG: CONF conf/bitbake.conf:541: including conf/local.conf
>>> DEBUG: CONF including /home/moko/build/conf/local.conf
>>> DEBUG: CONF conf/bitbake.conf:546: including conf/build/i686-linux.conf
>>> DEBUG: CONF file 'conf/build/i686-linux.conf' not found
>>> DEBUG: CONF conf/bitbake.conf:547: including
>>> conf/target/INVALID-INVALID.conf
>>> DEBUG: CONF file 'conf/target/INVALID-INVALID.conf' not found
>>> DEBUG: CONF conf/bitbake.conf:548: including conf/machine/x86.conf
>>> DEBUG: CONF including /home/moko/openembedded/conf/machine/x86.conf
>>> DEBUG: BB conf/machine/include/tune-x86.inc: handle(data, include)
>>> DEBUG: CONF conf/bitbake.conf:549: including conf/distro/openmoko.conf
>>> DEBUG: CONF including /home/moko/openembedded/conf/distro/openmoko.conf
>>> DEBUG: BB conf/distro/include/preferred-om-2008-versions.inc:
>>> handle(data, include)
>>> DEBUG: BB conf/distro/include/angstrom-2007-for-openmoko.inc:
>>> handle(data, include)
>>> DEBUG: BB conf/distro/include/sane-srcdates.inc: handle(data, include)
>>> DEBUG: BB conf/distro/include/sane-srcrevs.inc: handle(data, include)
>>> DEBUG: BB conf/distro/include/preferred-xorg-versions.inc: handle(data,
>>> include)
>>> DEBUG: BB conf/distro/include/preferred-gpe-versions-2.8.inc:
>>> handle(data, include)
>>> DEBUG: BB conf/distro/include/preferred-e-versions.inc: handle(data,
>>> include)
>>> DEBUG: BB conf/distro/include/angstrom.inc: handle(data, include)
>>> DEBUG: update_data()
>>> DEBUG: BB conf/distro/include/angstrom-glibc.inc: handle(data, include)
>>> DEBUG: BB conf/distro/include/angstrom-package-opk.inc: handle(data,
>>> include)
>>> DEBUG: update_data()
>>> DEBUG: CONF conf/bitbake.conf:550: including conf/documentation.conf
>>> DEBUG: CONF including /home/moko/openembedded/conf/documentation.conf
>>> DEBUG: setVarFlag(PREFERRED_VERSION, doc, Normally use it as
>>> PREFERRED_VERSION_package-name = "" to set the preferred version of more
>>> than one version for the package-name is available., data)
>>> DEBUG: setVarFlag(BUILD_ARCH, doc, The name of the building
>