Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/sqlite: fix parallel build failures
Date: Thu, 21 May 2015 20:10:21 +0200	[thread overview]
Message-ID: <20150521201021.111da6b5@free-electrons.com> (raw)
In-Reply-To: <20150521180609.GA4244@free.fr>

Dear Yann E. MORIN,

On Thu, 21 May 2015 20:06:10 +0200, Yann E. MORIN wrote:

> Full story:
> 
>   - sqlite uses fossil as its VCS;
> 
>   - cloning a fossil repo creates a single file (the DB) in the current
>     directory;
> 
>   - "checking out" the repository is also done in the curent directory,
>     polluting it;
> 
>   - there is no "fossil log" command;
> 
>   - the content of the fossil repository is clearly not aligned with
>     that of the tarball;
> 
>   - there is autostuff in the repository, but it is in a sub-dorectory,
>     and there is no explanation on how to use it; there is no explanation
>     on how to generate the archive from the repository;
> 
>   - the mailing list are not very newbie-friendly: they are
>     subscription-only (OK) but even the archives require subscription to
>     be browsed (not OK).
> 
> So, in the end, I just threw in the towel...

Seems fun :)

Maybe you could just send a mail to the mailing list to report the bug,
as suggested at https://www.sqlite.org/src/wiki?name=Bug+Reports ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-05-21 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 21:58 [Buildroot] [PATCH] package/sqlite: fix parallel build failures Yann E. MORIN
2015-05-21 10:07 ` Thomas Petazzoni
2015-05-21 18:06   ` Yann E. MORIN
2015-05-21 18:10     ` Thomas Petazzoni [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=20150521201021.111da6b5@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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