Building intel s2600wf image

[Andrew Jeffery]

Hi Wim,

On Fri, 15 Feb 2019, at 02:51, Wim Vervoorn wrote:
> Hello,
> 
> We are trying to build the Intel s2600wf image using the latest OpenBMC 
> tree. If we do that we are running into build errors.
> 
> Before digging into this can you tell me which commit of the tree can be 
> used to build an image for  this device without errors. This allows us 
> to have a stable version for reference.

Sorry to say this, but what you've written is a textbook example of how not
to ask for help :/

Things I don't know from the above:

1. What "the latest" OpenBMC tree is
2. What environment you're trying to build it in
3. How you are configuring and invoking the build
4. What error you are actually hitting
5. Whether you have searched the issue tracker for others reporting the
same problem

Regarding 1, we have a very definite way of identifying versions: The
commit ID of the openbmc/openbmc repository. OpenBMC is a fast
moving project, and your "latest" tree might not look like my "latest"
tree. Please make sure to provide the output of `git rev-parse HEAD`
from your working directory with your issues/queries.

Regarding 2, are you building on a physical or virtual machine? What
OS are you running? How much RAM and disk space do you have
available for the build (at a guess you should probably have at least
8GiB of RAM and 50GiB of disk space free). Which OS you're running
influences which compilers you have available for bootstrap and if
they're too old or too new they may cause issues. Please describe
your full environment.

Regarding 3, it's not clear if you've even configured yourself to build
a s2600wf image like you're claiming, or if you're correctly invoking
bitbake. Please provide the exact commands you used to configure
and build your image.

Regarding 4 there's literally nothing we can do to help you other than
say "Commit ID X works for me" in response. This may even be the
same commit that you're failing to build. If we know the details of 
the problem then if it is something unexpected we can help fix it.
This means you need to provide the failure output from bitbake,
*and* any logs that output might reference.

Finally, regarding 5, the best way to get help is often to help yourself.
Please make sure you've searched the issue tracker before asking
for help on the mailing list. In fact, typically, you'll get a better response
by actually opening a new issue if you have a new problem, as it gives
us a central point to collaborate around to resolve your problem.

I hope the above isn't too much of an affront, but I'm trying to help
you help us help you. We'll all be better off if you can provide us with
more information and make proper use of the systems we have in
place to deal with bugs.

Cheers,

Andrew