From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Build librsvg-2.34.2 Error
Date: Fri, 3 Feb 2012 10:22:21 -0500 [thread overview]
Message-ID: <CA+czFiB9n=d+SMfaDMU9N2-HGvxXzL0vFpnKKek8_jsazFbw5A@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiD8GSsmdpukbx8P0r9sAXr5ROstLve+70SKBPqsejSO9w@mail.gmail.com>
On Fri, Feb 3, 2012 at 10:19 AM, Michael Mol <mikemol@gmail.com> wrote:
> On Fri, Feb 3, 2012 at 9:51 AM, 高金培 <gjp1120@gmail.com> wrote:
>> CC librsvg_2_la-librsvg-enum-types.lo
>> /bin/sh ./libtool --silent --tag=CC --mode=compile i686-pc-linux-gnu-gcc
>> -DHAVE_CONFIG_H -I. -I. -I. -DG_LOG_DOMAIN=\"librsvg\"
>> -DLIBRSVG_DATADIR="\"/usr/share\"" -pthread -I/usr/include/gdk-pixbuf-2.0
>> -I/usr/include/libpng15 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
>> -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/freetype2
>> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm
>> -I/usr/include/libcroco-0.6 -I/usr/include/glib-2.0
>> -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DHAVE_LIBCROCO=1 -O2
>> -march=pentium-m -pipe -c -o librsvg_2_la-librsvg-enum-types.lo `test -f
>> 'librsvg-enum-types.c' || echo './'`librsvg-enum-types.c
>> CCLD librsvg-2.la
>> CCLD rsvg-convert
>> GISCAN Rsvg-2.0.gir
>> CCLD rsvg-view
>
>
>> In file included from <stdin>:19:0:
>> /var/tmp/portage/gnome-base/librsvg-2.34.2/work/librsvg-2.34.2/rsvg-cairo-render.h:32:19:
>> fatal error: cairo.h: No such file or directory
>> compilation terminated.
>
> I suspect you don't have cairo emerged.
>
>> * If you need support, post the output of 'emerge --info
>> =gnome-base/librsvg-2.34.2',
>> * the complete build log and the output of 'emerge -pqv
>> =gnome-base/librsvg-2.34.2'.
>> * The complete build log is located at
>> '/var/tmp/portage/gnome-base/librsvg-2.34.2/temp/build.log'.
>> * The ebuild environment file is located at
>> '/var/tmp/portage/gnome-base/librsvg-2.34.2/temp/environment'.
>> * S: '/var/tmp/portage/gnome-base/librsvg-2.34.2/work/librsvg-2.34.2'
>
> Before you go any farther, save the output of the commands it's asking about.
>
> sudo emerge --info gnome-base/librsvg-2.34.2 >
> ~/emerge.info.gnome-base.librsvg-2.34.2.txt
> sudo emerge -pqv gnome-base/librsvg-2.34.2 >
> ~/emerge.pqv.gnome-base.librsvg-2.34.2.txt
> sudo cp /var/tmp/portage/gnome-base/librsvg-2.34.2/temp/build.log
> ~/build.log.gnome-base.librsvg-2.34.2.txt
> sudo cp /var/tmp/portage/gnome-base/librsvg-2.34.2/temp/environment
> ~/environment.gnome-base.librsvg-2.34.2.txt
>
> If you need to file a bug report, you'll need to attach those to it.
>
> To install cairo, try
>
> emerge x11-libs/cairo
>
> Assuming that works, try
>
> emerge --resume
>
> If the build works, you should be good. If you get the same error,
> then you should file a bug report at bugs.gentoo.org.
Actually, you should file a bug report either way, but the nature of
the bug is different. If emerging cairo fixes the build error, then
there's a dependency missing in the ebuild. If emerging cairo doesn't
fix the build error, something else is broken that I don't have a clue
about.
--
:wq
next prev parent reply other threads:[~2012-02-03 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 14:51 [gentoo-user] Build librsvg-2.34.2 Error 高金培
2012-02-03 15:19 ` Michael Mol
2012-02-03 15:22 ` Michael Mol [this message]
2012-02-03 17:15 ` Alan McKinnon
2012-02-04 7:30 ` C Study
2012-02-03 15:50 ` Alex Schuster
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='CA+czFiB9n=d+SMfaDMU9N2-HGvxXzL0vFpnKKek8_jsazFbw5A@mail.gmail.com' \
--to=mikemol@gmail.com \
--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