I just wanted to follow up on your concerns regarding the patch-errors you reported.
LTIB uses three different "pools" of patches; global (GPP), local (LPP), and private (CPP).
You won't ever be able to get patches out of the private pool as it is only accessible from within Freescale's network. Hence this error that you reported below:
Posted By GG1 on 31 Dec 1969 6:0 PM
Testing network connectivity
FAILED CPP_STAGE: : 500 Can''t connect to auslxsc02.mtwk.freescale.net:80 (Bad hostname ''auslxsc02.mtwk.freescale.net'')
As you can see, the error is letting you know that it cannot connect to a machine named auslxsc02.mtwk.freescale.net
- again, because you aren't inside
Freescale's private network.
The other errors you reported are LTIB telling you that it was looking for patches but instead of finding them in the global or private patch pools (GPP and CPP), it found them in the local patch pool (LPP).
Posted By GG1 on 20 Dec 2007 8:26 AM
FAILED GPP_STAGE: u-boot-1.1.6-mpc8360ece-1.patch: 404 Not Found
FAILED CPP_STAGE: u-boot-1.1.6-mpc8360ece-1.patch: 500 Can''t connect to auslxsc02.mtwk.freescale.net:80 (Bad hostname ''auslxsc02.mtwk.frees
OK LPP_STAGE: u-boot-1.1.6-mpc8360ece-1.patch
In that error, LTIB was looking for a patch named u-boot-1.1.6-mpc8360ece-1.patch
. It first looked in the global patch pool (GPP) and didn't find it there. Then it looked for the patch in the private patch pool (CPP) - but couldn't connect. Finally, it found the patch in the local patch pool (LPP).
So, errors like that should be fine and not indicative of any problems with your install.
, I am concerned about your statement regarding it being necessary for you to disable microwindows. Can you please confirm that that truly is the case? Or, perhaps you could simply send the entire build log output from trying to do a microwindows enabled build?