public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: David Haller <gentoo@dhaller.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Inkscape failed to compile...(update from this morning)
Date: Sun, 28 Oct 2018 08:05:22 +0100	[thread overview]
Message-ID: <20181028070522.fta7zdyzssgsivs4@grusum.endjinn.de> (raw)
In-Reply-To: <20181028064637.5hkv74qy34j5l5e7@solfire>

Hello,

On Sun, 28 Oct 2018, tuxic@posteo.de wrote:
[..]
>reemergeing cairomm fixes the problem!

No wonder. The error was e.g.:
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../lib64/libcairomm-1.0.so:
undefined reference to `cairo_script_create'

$ qfile /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../lib64/libcairomm-1.0.so
dev-cpp/cairomm (/usr/lib64/libcairomm-1.0.so)

So re-emerging dev-cpp/cairomm should be obvious ;)

>Unfortunately I emerged and forget the '-1'...is there a 
>way to fix that?

# sed -i.orig '/^dev-cpp/cairomm$/d' /var/lib/portage/world

Check with

# diff -u /var/lib/portage/world.orig /var/lib/portage/world

that only that one entry is gone. Then you can remove the .orig.

Or just edit that world file with the editor of your choice.

HTH,
-dnh

-- 
I don't care about people reading in OE. It just gets bad if they
send postings, viruses, and complaints about non-existing attachements.


  reply	other threads:[~2018-10-28  8:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28  3:29 [gentoo-user] Inkscape failed to compile...(update from this morning) tuxic
2018-10-28  3:54 ` Dale
2018-10-28  4:41   ` tuxic
2018-10-28  5:08     ` Adam Carter
2018-10-28  5:13       ` Adam Carter
2018-10-28  6:46         ` tuxic
2018-10-28  7:05           ` David Haller [this message]
2018-10-28  8:29             ` tuxic
2018-10-28  8:49           ` Peter Humphrey
2018-10-28  9:05             ` tuxic
2018-10-28  9:55               ` Peter Humphrey

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=20181028070522.fta7zdyzssgsivs4@grusum.endjinn.de \
    --to=gentoo@dhaller.de \
    --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