From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc-2.27 is broken
Date: Tue, 30 Oct 2018 14:52:41 -0400 [thread overview]
Message-ID: <20181030185241.GG1931@ca.inter.net> (raw)
In-Reply-To: <de0a8617-3ea0-0e80-7cde-1652bfbab8bd@mail.ru>
181030 the wrote:
> I have upgraded to sys-libs/glibc-2.27-r6 and it broke the system.
> I can't even compile a hello world test program in c.
> I always get the following linking error:
> $ gcc main.c -o main.elf
> /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld:
> /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../lib64/crtn.o(a.debug_info+0x1000300000000):
> reloc against `*UND*': error 4
> /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld:
> final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status
> When I try to install something it fails during configuration
> at compiler sanity check.
I updated to this version of Glibc 181027 & emerged other pkgs successfully.
I don't use the 'multiarch' USE flag.
> Should I report this as a bug or is there's something wrong with me ?
I'm sure there's nothing wrong with you (smile),
but there mb a USE flag or similar which needs changing.
NB above : the error you cite is '4' :
this shows there are other errors '1' '2' '3' above, which are more important.
It would help if you find them & report them to the list.
No doubt others will offer more detailed advice.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next prev parent reply other threads:[~2018-10-30 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 18:27 [gentoo-user] glibc-2.27 is broken the
2018-10-30 18:52 ` Philip Webb [this message]
2018-10-30 19:02 ` the
2018-11-01 0:12 ` Andrew Savchenko
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=20181030185241.GG1931@ca.inter.net \
--to=purslow@ca.inter.net \
--cc=gentoo-user@lists.gentoo.org \
/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