From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.devel Subject: Re: Emacs master build failing on RHEL 6.8 [image.c] Date: Tue, 4 Jun 2019 15:36:33 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000553a04058a849b91" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="205590"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Emacs developers To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 04 21:39:23 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hYFHC-000rFa-Si for ged-emacs-devel@m.gmane.org; Tue, 04 Jun 2019 21:39:18 +0200 Original-Received: from localhost ([127.0.0.1]:57045 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hYFHB-0007Wj-Pm for ged-emacs-devel@m.gmane.org; Tue, 04 Jun 2019 15:39:17 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:51371) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hYFFF-0006A4-5c for emacs-devel@gnu.org; Tue, 04 Jun 2019 15:37:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hYFFE-0003QK-6G for emacs-devel@gnu.org; Tue, 04 Jun 2019 15:37:17 -0400 Original-Received: from mail-lj1-x22c.google.com ([2a00:1450:4864:20::22c]:35989) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hYFFD-0003J5-S7 for emacs-devel@gnu.org; Tue, 04 Jun 2019 15:37:16 -0400 Original-Received: by mail-lj1-x22c.google.com with SMTP id i21so6304186ljj.3 for ; Tue, 04 Jun 2019 12:37:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RShjEFdpOs7McOM8OmFvjwGnFXy9uKSL7eLe5HDqACw=; b=YHHnadP7Mlm/BPc7KyY5lZSgXpMZCn4Nq3CsKdAZbg1YXgoA5TB/5gsVFL1TIiiU9b uEg+p1sdpbqoiHqbA9EKGHdhYpT6xU22627Duv0SghhDIlCwCKpOYuuCZZZeO+4wqaDn 2tLHQqCRnqOZWkxohSPKffRXrUuJKYcV0m1js8Lcjg5kOv9SzyMV0FIb8dfZ67cmG1Tk fOamm4LcyN61dr6MbjvM/c6GQJFM1vSUqHEpxVLEtiIUFhXFDwMmh2VcNvLGEvtjlqwG ihXOcSiFlhzeJvPXPftXVjM56BCGeGAvG+T5FCdrPfYD1mmiiKqLC12RhClH3sHGZf3y Qf2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RShjEFdpOs7McOM8OmFvjwGnFXy9uKSL7eLe5HDqACw=; b=GnZTk9hpVrpvThEgkk647j1FLWjv7VwTcTT0Wrz5cdxuSVq1qHjoO1yGDfYjmZ9OVU /TKY+K/+34VEaJKVpwr82ArWm9GnkakkAz77xHSVkrZZHmZQlNL7Clsu7O5vpt9XH+ng dyggAVJzfQV9l06gnKUPIAItwYJcMOS4gmDt+k3m9AuGn8+Vhok64jVq3aEm/paT1ybi E6BzeEDkHQnh2j76cG0RDAuvZSe3AvZG5Mh1WlILQD4erE2TEeG4f7sTamFq0VfsaPiB 0PxzDVZMxj2UpQ/YkLnwtZJ3nPji/rLSl8PxjX/8zP1wsRsNCEDuJaI4lCzSIxMxR4eh 5xAw== X-Gm-Message-State: APjAAAWxrndMcTAKb8PUQmKiTEDohhA15xw8Pzh5Cw/dVMg8Hrygd9JL EVxdyNWiIx0dl8ic0GYQZ9loKJTr6q8c6x5A1kM= X-Google-Smtp-Source: APXvYqzQgyM5VwEn4HGcZhzMYtkW4Cz4pjYRW2NnliUokZB84tBtg6WBNYS9CtccEqrEBMNuWUJUNltmZDxd8Ta6C1Y= X-Received: by 2002:a2e:9e1a:: with SMTP id e26mr3442925ljk.158.1559677029921; Tue, 04 Jun 2019 12:37:09 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::22c X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:237255 Archived-At: --000000000000553a04058a849b91 Content-Type: text/plain; charset="UTF-8" Hello Paul, On Tue, Jun 4, 2019 at 3:17 PM Paul Eggert wrote: > > This looks like some other glitch in your build process, something you > should fix but unrelated to the GifErrorString problem. > You are right! I reverted to the old commit where I was last able to build and I am seeing the same error. I need to now figure out what change on my side could have caused this. Sorry for this false alarm. I'll update here if I figure this out. --000000000000553a04058a849b91 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Paul,

On = Tue, Jun 4, 2019 at 3:17 PM Paul Eggert <eggert@cs.ucla.edu> wrote:

This looks like some other glitch in your build process, something you
should fix but unrelated to the GifErrorString problem.

You are right! I reverted to the old commit where I was la= st able to build and I am seeing the same error.

I= need to now figure out what change on my side could have caused this. Sorr= y for this false alarm.

I'll update here if I = figure this out.
--000000000000553a04058a849b91--