all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Rene <pacoon@protonmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
	"bug-hurd@gnu.org" <bug-hurd@gnu.org>,
	Manolis Ragkousis <manolis837@gmail.com>
Subject: Re: About GCC-5.5.0
Date: Fri, 25 May 2018 01:41:30 +0200	[thread overview]
Message-ID: <20180524234130.l4vr6tt435igokvj@var.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <6NS5gP1LFQIB0z7F0KrTwSUjfE3VptjXDIyh_Cat5yxILxKmvKjjOiyA5zUzwNfsP0ARyGwKLnK17FNI9LZmKvh8jiq4ZUDiTxahbFND_cA=@protonmail.com>

Hello,

Rene, le mer. 23 mai 2018 22:57:21 -0400, a ecrit:
> I am updating my Guix repository on Debian/Hurd and I have the following error
> in the 'configure' phase of glibc(glibc-intermediate-2.23).
> We have tried to add the flag '-fno-stack-protector' to glibc, however the
> error remains.
> 
> Any idea of how we can approach it?

Getting the config.log would allow to have more ideas :)

> ---
>           checking if i586-pc-gnu-gcc accepts
> -fno-tree-loop-distribute-patterns with __at
>           tribute__ ((__optimize__))... yes
>           checking for libgd... no
>           checking for is_selinux_enabled in -lselinux... no
>           checking for _FORTIFY_SOURCE predefine... no       
>           checking whether i586-pc-gnu-gcc implicitly enables
> -fstack-protector... configu
>           re: error: unexpected symbols in test:    
> ---
> 
> 
> Thank you
> Rene

  reply	other threads:[~2018-05-24 23:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24  2:57 About GCC-5.5.0 Rene
2018-05-24 23:41 ` Samuel Thibault [this message]
2018-05-25  2:28   ` Rene
2018-05-25  4:03     ` Rene
2018-05-28  9:48     ` Ludovic Courtès
2018-05-29 12:30       ` Rene

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=20180524234130.l4vr6tt435igokvj@var.youpi.perso.aquilenet.fr \
    --to=samuel.thibault@gnu.org \
    --cc=bug-hurd@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=manolis837@gmail.com \
    --cc=pacoon@protonmail.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.