All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools: buildman: prevent trying to use the working directory as build dorectory
Date: Fri, 14 Jul 2017 08:57:05 +0200	[thread overview]
Message-ID: <20170714085705.4160b3ea@karo-electronics.de> (raw)
In-Reply-To: <CAPnjgZ0vi93Ffs9P3Voe+E-=_Q0+J1pnGaVhACStFZDzAs5hgg@mail.gmail.com>

Hi,

On Thu, 13 Jul 2017 13:09:58 -0600 Simon Glass wrote:
> On 5 July 2017 at 01:34, Lothar Waßmann <LW@karo-electronics.de> wrote:
> > When the U-Boot base directory happens to have the same name as the
> > branch that buildman is directed to use via the '-b' option and no
> > output directory is specified with '-o', buildman happily starts
> > removing the whole U-Boot sources eventually only stopped with the
> > error message:
> > OSError: [Errno 20] Not a directory: '../<branch-name>/boards.cfg
> >
> > Add a check to the builderthread.Mkdir function to verify that the
> > path it tries to create does not match the current working
> > directory.
> >
> > Signed-off-by: Lothar Waßmann <LW@KARO-electronics.de>
> > ---
> >  tools/buildman/builderthread.py | 4 ++++
> >  1 file changed, 4 insertions(+)
> 
> That's nasty, thanks for the fix.
> 
> But this is being done inside each thread so I'm not sure how this
> will be reported, or whether buildman will stop correctly.
> 
> Can the check happen before the build even starts, perhaps? E,g, in builder.py?
> 
I don't have the time to look deeper into this, perhaps someone more
involved with the builman scripts can have a look into this.


Lothar Waßmann

  reply	other threads:[~2017-07-14  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05  7:34 [U-Boot] [PATCH] tools: buildman: prevent trying to use the working directory as build dorectory Lothar Waßmann
2017-07-13 19:09 ` Simon Glass
2017-07-14  6:57   ` Lothar Waßmann [this message]
2018-04-02  8:43     ` Simon Glass

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=20170714085705.4160b3ea@karo-electronics.de \
    --to=lw@karo-electronics.de \
    --cc=u-boot@lists.denx.de \
    /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.