Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] package/trinity: New package
Date: Mon, 20 Oct 2014 11:13:49 +0100	[thread overview]
Message-ID: <5444E05D.5070008@imgtec.com> (raw)
In-Reply-To: <CAHXCMML2_6s4Wn6PEVoOK396vPr+M5jbf+258Q02oLmsNvGdFg@mail.gmail.com>

Dear Samuel Martin,

On 10/11/2014 04:47 PM, Samuel Martin wrote:
> On Sat, Oct 11, 2014 at 4:03 PM, Vincent Olivert Riera
> <Vincent.Riera@imgtec.com> wrote:
>> Dear Samuel Martin,
>>
>> it's very weird. I just used your defconfig and everything was fine. Look:
>>
>> [...]
>> /usr/bin/install -m 0644 support/misc/target-dir-warning.txt /home/peratu/downloads/buildroot/output/target/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM
>> $ make savedefconfig && cat defconfig
>> BR2_arm=y
>> BR2_TOOLCHAIN_EXTERNAL=y
>> BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
>> BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
>> BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-basic-2014.08.tar.bz2"
>> BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_16=y
>> # BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
>> BR2_PACKAGE_TRINITY=y
>>
>
> Humm... indeed weird! :-|
>
> For the record, the gen-versionh.sh trace:
> http://code.bulix.org/kn3whb-87181/?raw
> I got this doing:
> $ make trinity-dirclean
> $ make trinity-configure
> # add 'set -x' right after /bin/bash in
> <output>/build/trinity-780d879c71979f54dfc9ec0a26e6f1e0d5e361e1/scripts/gen-versionh.sh
> $ make trinity
>
> Maybe you'll be able to find something.
>
> Regards,
>
>> Regards,
>>
>> --
>> Vincent
>> ________________________________________
>> From: Samuel Martin [s.martin49 at gmail.com]
>> Sent: 11 October 2014 14:40
>> To: Vincent Olivert Riera
>> Cc: buildroot
>> Subject: Re: [Buildroot] [PATCH v4] package/trinity: New package
>>
>> Hi Vicente,
>>
>> On Sat, Oct 11, 2014 at 2:57 PM, Vincent Olivert Riera
>> <Vincent.Riera@imgtec.com> wrote:
>>> Dear Samuel Martin,
>>>
>>> can you provide a defconfig which fails? I have built it twice few minutes ago.
>>
>> Here it is: http://code.bulix.org/4oyy7r-87179/?raw
>>
>> And here the build error: http://code.bulix.org/j2n1a8-87180/?raw
>>
>> (I've just apply the patch from patchwork on top of master).
>>
>>>
>>> Also, it will be faster if you send an email directly to the maintainer instead of a pull request, as it's said in the "Downloads:" section of trinity's website.
>>
>> Oops, forgot to check that :-s
>> I will send a mail.
>>
>> Regards,
>>
>>
>> --
>> Samuel
>
>
>

Your patches have been merged upstream. I will send a v5 patch and I 
would like you test it, please.

Best regards,

-- 
Vicente Olivert Riera
Graduate Software Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com

      reply	other threads:[~2014-10-20 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 15:15 [Buildroot] [PATCH v4] package/trinity: New package Vicente Olivert Riera
2014-10-10 21:03 ` Samuel Martin
2014-10-11 12:57   ` Vincent Olivert Riera
2014-10-11 13:40     ` Samuel Martin
2014-10-11 14:03       ` Vincent Olivert Riera
2014-10-11 15:47         ` Samuel Martin
2014-10-20 10:13           ` Vicente Olivert Riera [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=5444E05D.5070008@imgtec.com \
    --to=vincent.riera@imgtec.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox