Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/bayer2rgb-neon: bump version
Date: Thu, 4 Apr 2019 22:19:25 +0200	[thread overview]
Message-ID: <20190404221925.7faa6db5@windsurf> (raw)
In-Reply-To: <20190403211231.99053-1-giulio.benetti@micronovasrl.com>

Hello Giulio,

On Wed,  3 Apr 2019 23:12:31 +0200
Giulio Benetti <giulio.benetti@micronovasrl.com> wrote:

> Actually build fails with musl libc due to missing header inclusion
> <unistd.h> (usually included by stdlib.h) in package code which in order
> contains type definition of ssize_t.
> A Git repository has been setted up for this project as upstream, and
> contains a commit which solves build failure removing the use of ssize_t
> at all.
> No other http tarballs have been released on current site, so
> development seems to continue on Git repository.
> 
> - Set SITE_METHOD = git
> - Switch site to: https://gitlab-ext.sigma-chemnitz.de/ensc/bayer2rgb
> - Bump version to latest commit to include commit which fixes build
>   failure.
> 
> Fixes:
> http://autobuild.buildroot.net/results/c84/c84b65642cb1b2d246f3a92ac957af5c5fcb86e8/
> 
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>

Do we have an indication of what is the real upstream location for this
project ?

You're saying "a Git repo has been set up for this project as
upstream". What indication you have that this is the most "official"
upstream ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-04-04 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 21:12 [Buildroot] [PATCH] package/bayer2rgb-neon: bump version Giulio Benetti
2019-04-04 20:19 ` Thomas Petazzoni [this message]
2019-04-04 20:27   ` Giulio Benetti
2019-04-07  6:47 ` Peter Korsgaard

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=20190404221925.7faa6db5@windsurf \
    --to=thomas.petazzoni@bootlin.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