All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] glibc: Upgrade to 2.23
Date: Mon, 22 Feb 2016 17:38:01 +0100	[thread overview]
Message-ID: <20160222163801.GF6329@jama> (raw)
In-Reply-To: <CAMKF1srkT1+nYhnjdtC15DyfWN-RRrjNbd0k1_gu578kg0XA1g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

On Mon, Feb 22, 2016 at 08:19:08AM -0800, Khem Raj wrote:
> Can you clone it outside oe

Yes, (at least now)

> On Feb 22, 2016 7:48 AM, "Martin Jansa" <martin.jansa@gmail.com> wrote:
> 
> > On Sat, Feb 20, 2016 at 08:07:25AM +0000, Khem Raj wrote:
> > > Drop kconfig and options-group support
> > > Forward port cross-localedef support
> > > Assume ssp support in libc when building gcc-initial
> >
> > Unfortunately sourceware git doesn't like us, glibc is failing to fetch :/
> >
> > ERROR: glibc-initial-2.23-r0 do_fetch: Fetcher failure: Fetch command
> > failed with exit code 128, output:
> > fatal: read error: Connection reset by peer
> >
> > ERROR: glibc-initial-2.23-r0 do_fetch: Function failed: Fetcher failure
> > for URL:
> > 'git://sourceware.org/git/glibc.git;branch=release/2.23/master;name=glibc
> > '.
> > Unable to fetch URL from any source.
> > ERROR: Logfile of failure stored in:
> >
> > /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5e-oe-linux-gnueabi/glibc-initial/2.23-r0/temp/log.do_fetch.31233
> > NOTE: recipe glibc-initial-2.23-r0: task do_fetch: Failed
> >

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2016-02-22 16:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20  8:06 [PATCH 0/3] Upgrade glibc 2.23 Khem Raj
2016-02-20  8:07 ` [PATCH 1/3] glibc: Upgrade to 2.23 Khem Raj
2016-02-22 15:49   ` Martin Jansa
2016-02-22 16:19     ` Khem Raj
2016-02-22 16:38       ` Martin Jansa [this message]
2016-02-22 22:31   ` Andre McCurdy
2016-03-29  1:38     ` ChenQi
2016-03-29  2:16       ` Khem Raj
2016-03-31  7:01         ` ChenQi
2016-04-01  8:44           ` ChenQi
2016-04-01 14:11             ` Khem Raj
2016-02-20  8:07 ` [PATCH 2/3] pseudo: Fix build when security flags are enabled Khem Raj
2016-02-20  8:07 ` [PATCH 3/3] libnewt: Fix build with PIE flags Khem Raj

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=20160222163801.GF6329@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.