rtems source builde git repository

[Hoefle Marco]

Dear Chris,
thank you for your quick response. From the doku I understand that the syntax has changed.
I should use 
%source set rtems_gr-4.10 git.nanotronic:rtems.git?reset=hard?pull?branch=gr-4.10

However I wanted to have a look how the other builds are working. Thus I checked out the latest commit from 2014-08-09
sb: Add INI format output to the reports.    
    The INI format report is a way to export a configuration.

There I wanted to build the normal sparc toolchain + rtems Kernel before I proceed with our gaisler patched rtems git tree:

hoefle at wheezy:~/projects/customers/unibern/cassis/clone/source_build_test/scripts$ cd ..
hoefle at wheezy:~/projects/customers/unibern/cassis/clone/source_build_test$ CUR_DIR=$PWD
hoefle at wheezy:~/projects/customers/unibern/cassis/clone/source_build_test$ TOOLCHAIN_DIR=$CUR_DIR/build/toolchain
hoefle at wheezy:~/projects/customers/unibern/cassis/clone/source_build_test$ RTEMS_SOURCE_BUILDER=$CUR_DIR/
hoefle at wheezy:~/projects/customers/unibern/cassis/clone/source_build_test$ mkdir -p $TOOLCHAIN_DIR
hoefle at wheezy:~/projects/customers/unibern/cassis/clone/source_build_test$ cd rtems-source-builder/rtems
hoefle at wheezy:~/projects/customers/unibern/cassis/clone/source_build_test/rtems-source-builder/rtems$ ../source-builder/sb-set-builder --log=$TOOLCHAIN_DIR/4.10-sparc.log --prefix=$TOOLCHAIN_DIR --no-clean 4.10/rtems-sparc.bset
RTEMS Source Builder - Set Builder, v0.4.0
Build Set: 4.10/rtems-sparc.bset
config: devel/expat-2.1.0-1.cfg
package: expat-2.1.0-x86_64-linux-gnu-1
Build Set: Time 0:00:00.079997
Traceback (most recent call last):
  File "../source-builder/sb-set-builder", line 26, in <module>
    setbuilder.run()
  File "../source-builder/sb/setbuilder.py", line 468, in run
    b.build(deps)
  File "../source-builder/sb/setbuilder.py", line 343, in build
    self.build_package(configs[s], b)
  File "../source-builder/sb/setbuilder.py", line 179, in build_package
    _build.make()
  File "../source-builder/sb/build.py", line 421, in make
    self.prep(package)
  File "../source-builder/sb/build.py", line 317, in prep
    self.source_setup(package, args[1:])
  File "../source-builder/sb/build.py", line 219, in source_setup
    for source in self.source(setup_name):
  File "../source-builder/sb/build.py", line 173, in source
    src = download.parse_url(url, '_sourcedir', self.config, self.opts)
  File "../source-builder/sb/download.py", line 222, in parse_url
    _hash_check(source['file'], local, config.macros)
  File "../source-builder/sb/download.py", line 56, in _hash_check
    hash = sources.get_hash(file_.lower(), macros)
NameError: global name 'sources' is not defined


This was how I used rtems source builder before, is there something missing when trying v0.4.0?
Thanks,
Marco





-----Original Message-----
From: Chris Johns [mailto:chrisj at rtems.org]
Sent: Sat 09/08/2014 05:11
To: Hoefle Marco; users at rtems.org
Subject: Re: rtems source builde git repository
 
On 9/08/2014 1:01 am, Hoefle Marco wrote:
> Hello,
> in rtems source build commit 2be445d2aafae21849c5d626b3787e2ab1ac846b
> this works:
>
> %define Source0 git.nanotronic:rtems.git?reset=hard?pull?branch=gr-4.10
>
> rtems source builder output:
> git: reset: git.nanotronic:rtems.git
> git: pull: git.nanotronic:rtems.git
> git: checkout: git.nanotronic:rtems.git => gr-4.10
>
> With the latest commit 8c19df26f679f53f22144c43b3141278e19da80e (and
> commits before probably as well)
> rtems source builder complains about malformed url.
>
> Is this as the URL does not start with git:// ?
>

You have not provided any output so it is difficult to say. I suspect it 
is related to the changes I talk about below.

> Does anybody know why?

This commit ...

http://git.rtems.org/rtems-source-builder/diff/source-builder/sb/config.py?id=a083b52921a86a3bc49e2cc1d7d102612694557c

removed support for 'Source0' and 'Patch0'. Please refer to the 
documentation:

http://www.rtems.org/ftp/pub/rtems/people/chrisj/source-builder/source-builder.html#_source

for details.

The %source0, %source1, etc and %patch0, %patch1, etc were difficult to 
maintain and with this change there is no number and so no clashes. All 
you do is add the source or patch.

Chris




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20140811/24a33b0b/attachment-0002.html>