public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Emerge does want to tell me...what?
Date: Mon, 04 Dec 2017 10:34:48 +0000	[thread overview]
Message-ID: <1594976.Z0aQS8hZtE@peak> (raw)
In-Reply-To: <20171203175853.GB4340@anonymous>

On Sunday, 3 December 2017 17:58:53 GMT Simon Thelen wrote:
> On 17-12-03 at 09:52, Ian Zimmerman wrote:
> > On 2017-12-03 06:46, Heiko Baums wrote:
> > > 1. It can't find >=sys-devel/gcc-6.4.0 but only older gcc versions.
> > > 
> > > 2. You have installed a package that depend on sys-devel/gcc-5.4.0-r3
> > > or sys-devel/gcc-4.9.4.
> > > 
> > > I already explained what you can do in the first case. In the second
> > > case I would try to fix (uninstall, rebuild, upgrade or whatever)
> > > those packages which depend on an outdated gcc. I guess equery is your
> > > friend.
> > 
> > Those include palemoon.  GL with fixing that.
> 
> Palemoon builds fine with gcc 6.4.0 (just not with gcc 7.2.0), if the
> ebuild you're using requires an older gcc it's either wrong or doing
> something weird.

It doesn't build here; I get a few errors, thus:

 9:41.58 ../../build/unix/gold/ld: error: /var/tmp/portage/www-client/
palemoon-27.6.2/work/palemoon-27.6.2/o/toolkit/library/../../media/
libstagefright/Unified_cpp_media_libstagefright0.o: requires dynamic 
R_X86_64_PC32 reloc against '_Z13GetDemuxerLogv' which may overflow at 
runtime; recompile with -fPIC
 9:41.58 ../../build/unix/gold/ld: error: read-only segment has dynamic 
relocations
 9:41.58 /var/tmp/portage/www-client/palemoon-27.6.2/work/palemoon-27.6.2/
media/libstagefright/binding/MoofParser.cpp:767: error: undefined reference 
to 'GetDemuxerLog()'
...
ERROR: www-client/palemoon-27.6.2::palemoon failed (compile phase)

This is after upgrading to the 17.0 plasma profile, as instructed in the 
news item. Does it warrant a bug report?

-- 
Regards,
Peter.



  parent reply	other threads:[~2017-12-04 10:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03  4:43 [gentoo-user] Emerge does want to tell me...what? tuxic
2017-12-03  5:16 ` Heiko Baums
2017-12-03  5:29   ` tuxic
2017-12-03  5:46     ` Heiko Baums
2017-12-03  6:28       ` Dale
2017-12-03 17:52       ` [gentoo-user] " Ian Zimmerman
2017-12-03 17:58         ` Simon Thelen
2017-12-03 20:06           ` Ian Zimmerman
2017-12-03 21:45             ` Simon Thelen
2017-12-03 22:57               ` [gentoo-user] palemoon and gcc [Was: Emerge does want to tell me...what?] Ian Zimmerman
2017-12-04 10:34           ` Peter Humphrey [this message]
2017-12-04 19:19             ` [gentoo-user] Re: Emerge does want to tell me...what? Walter Dnes
2017-12-04 19:30               ` Walter Dnes
2017-12-05 10:23               ` Peter Humphrey
2017-12-05 13:18                 ` Michael Orlitzky
2017-12-05 14:02                   ` Peter Humphrey
2017-12-05 16:52                     ` Ian Zimmerman
2017-12-05 16:18                 ` Peter Humphrey
2017-12-05 16:49                   ` Raffaele Belardi
2017-12-06 10:11                     ` Peter Humphrey
2017-12-06 10:33                       ` Raffaele Belardi
2017-12-06 14:34                         ` Peter Humphrey
2017-12-03  9:13 ` [gentoo-user] " Adam Carter

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=1594976.Z0aQS8hZtE@peak \
    --to=peter@prh.myzen.co.uk \
    --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