All of lore.kernel.org
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] help on using buildman
Date: Thu, 20 Nov 2014 12:18:10 -0800	[thread overview]
Message-ID: <546E4C82.2010305@freescale.com> (raw)
In-Reply-To: <CAPnjgZ34SbKaUS3q+qQi9vtok6dpTjW0dWvYkCwKcHmhka=CEA@mail.gmail.com>

On 11/20/2014 12:10 PM, Simon Glass wrote:
> Hi York,
>>
>> I think the key is to configure it, not build it. With the failure case, it
>> doesn't build. I am thinking to find the equivalent to "make ARCH=power ...".
>> How to dump that?
> 
> Add a 'print' line to make() in builder.py:
> 
>         cmd = [self.gnu_make] + list(args)
>         print cmd
>         result = command.RunPipe([cmd], capture=True, capture_stderr=True,
>                 cwd=cwd, raise_on_error=False, **kwargs)
>         return result
> 

Thanks. Adding the "print cmd" makes the issue disappeared. Removing it, the
issue comes back. Add it back, it is gone again. I removed the working directory
each time before building it. See the commands below

$ !407
./tools/buildman/buildman -b working_upstream_qoriq --count=1 --keep-outputs
--force-build --force-reconfig MPC832XEMDS_HOST_66 -ve
No section: 'make-flags'
boards.cfg is up to date. Nothing to do.
Building 1 commit for 1 boards (1 thread, 24 jobs per thread)
Cloning repo for thread 0
    0    0    0 /1      (starting) ['make', 'mrproper', 'O=build', '-j', '24']
['make', 'O=build', '-j', '24', 'MPC832XEMDS_HOST_66_defconfig']
['make', 'O=build', '-j', '24']
01: arm: ls102xa: Select ge2_clk125 for eTSEC clock muxing
    1    0    0 /1      MPC832XEMDS_HOST_66
-bash-3.2$ git diff
diff --git a/tools/buildman/builder.py b/tools/buildman/builder.py
index 8155c16..0411959 100644
--- a/tools/buildman/builder.py
+++ b/tools/buildman/builder.py
@@ -324,6 +324,7 @@ class Builder:
             kwargs: Arguments to pass to command.RunPipe()
         """
         cmd = [self.gnu_make] + list(args)
+       print cmd
         result = command.RunPipe([cmd], capture=True, capture_stderr=True,
                 cwd=cwd, raise_on_error=False, **kwargs)
         return result
diff --git a/tools/buildman/builderthread.py b/tools/buildman/builderthread.py
index a9cf68a..d9526e6 100644
--- a/tools/buildman/builderthread.py
+++ b/tools/buildman/builderthread.py
@@ -197,7 +197,7 @@ class BuilderThread(threading.Thread):
                         src_dir = os.getcwd()
                     else:
                         args.append('O=build')
-                args.append('-s')
+#                args.append('-s')
                 if self.builder.num_jobs is not None:
                     args.extend(['-j', str(self.builder.num_jobs)])
                 config_args = ['%s_defconfig' % brd.target]
-bash-3.2$ git checkout tools/buildman/builder.py
-bash-3.2$ rm -rf ../working_upstream_qoriq/
-bash-3.2$ ./tools/buildman/buildman -b working_upstream_qoriq --count=1
--keep-outputs --force-build --force-reconfig MPC832XEMDS_HOST_66 -ve
No section: 'make-flags'
boards.cfg is up to date. Nothing to do.
Building 1 commit for 1 boards (1 thread, 24 jobs per thread)
Cloning repo for thread 0
01: arm: ls102xa: Select ge2_clk125 for eTSEC clock muxing
   powerpc: +   MPC832XEMDS_HOST_66
+make[1]: *** No rule to make target `../arch//cpu/u-boot.lds', needed by
`u-boot.lds'.  Stop.
+make: *** [sub-make] Error 2
    0    0    1 /1      MPC832XEMDS_HOST_66
-bash-3.2$ vi tools/buildman/builder.py
-bash-3.2$ rm -rf ../working_upstream_qoriq/-bash-3.2$ ./tools/buildman/buildman
-b working_upstream_qoriq --count=1 --keep-outputs --force-build
--force-reconfig MPC832XEMDS_HOST_66 -ve
No section: 'make-flags'
boards.cfg is up to date. Nothing to do.
Building 1 commit for 1 boards (1 thread, 24 jobs per thread)
Cloning repo for thread 0
    0    0    0 /1      (starting) ['make', 'mrproper', 'O=build', '-j', '24']
['make', 'O=build', '-j', '24', 'MPC832XEMDS_HOST_66_defconfig']
['make', 'O=build', '-j', '24']
01: arm: ls102xa: Select ge2_clk125 for eTSEC clock muxing
    1    0    0 /1      MPC832XEMDS_HOST_66
-bash-3.2$

I don't see ARCH defined anywhere.

York

  reply	other threads:[~2014-11-20 20:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 18:47 [U-Boot] help on using buildman York Sun
2014-11-20 19:13 ` Simon Glass
2014-11-20 19:22   ` York Sun
2014-11-20 19:46     ` York Sun
2014-11-20 19:51       ` Simon Glass
2014-11-20 19:55         ` York Sun
2014-11-20 20:10           ` Simon Glass
2014-11-20 20:18             ` York Sun [this message]
2014-11-20 21:04               ` York Sun
2014-11-20 21:33                 ` York Sun
2014-11-20 21:34                   ` York Sun
2014-11-20 21:46                     ` Simon Glass
2014-11-20 22:25                       ` York Sun
2014-11-20 23:35                         ` York Sun
2014-11-21  4:14                           ` Simon Glass
2014-11-21  4:42                             ` Masahiro Yamada
2014-11-21  4:53                               ` Masahiro Yamada
2014-11-21  4:55                               ` York Sun
2014-11-21  6:00                                 ` Masahiro Yamada
     [not found]                                   ` <E5C75E70-6F62-4E5C-9861-1D903D9BBFC9@freescale.com>
2014-11-21  6:47                                     ` York Sun
2014-11-21 17:14                                       ` York Sun
2014-11-21 17:22                             ` York Sun

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=546E4C82.2010305@freescale.com \
    --to=yorksun@freescale.com \
    --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.