From: Brian Woods <brian.woods@amd.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Brian Woods <brian.woods@amd.com>, xen-devel@lists.xen.org
Subject: Re: Build Inconsistencies
Date: Wed, 25 Jul 2018 09:41:48 -0500 [thread overview]
Message-ID: <20180725144146.GA4631@amd.com> (raw)
In-Reply-To: <20180725082706.nklcesfvfbrc63au@mac.bytemobile.com>
On Wed, Jul 25, 2018 at 10:27:06AM +0200, Roger Pau Monné wrote:
> I'm afraid I'm not able to find the error in the logs. I've tried
> grepping for 'error:' or '***', but I haven't been able to find
> anything.
>
> Do you happen to have the exact cause of the build failure?
>
>
> AFAICT a `make debball` doesn't call the clean targets, so you are
> doing something else here apart from a `make debball`.
>
> Thanks, Roger.
I just looked and it I accident did two make cleans rather than a clean
and build in the j120 log. It wasn't producing a deb though, after
doing cleans and distcleans it still wasn't producing a new debball.
I'm guessing it was transient because when I tried to reproduce it
again today, it was successful, repeatedly. Either way, sorry about
this. Next time this happens I'll make sure to pull a fresh copy to
double check rather than just a distclean.
--
Brian Woods
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-07-25 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180724164617.GA32193@amd.com>
2018-07-25 8:27 ` Build Inconsistencies Roger Pau Monné
2018-07-25 14:41 ` Brian Woods [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180725144146.GA4631@amd.com \
--to=brian.woods@amd.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.