public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] problem after sync + update libgdiplus
Date: Sun, 23 Sep 2007 19:51:43 +0200	[thread overview]
Message-ID: <d257c3560709231051o2f3a9391hd94da587a5ccc450@mail.gmail.com> (raw)
In-Reply-To: <1190561159.10537.13.camel@gentoo>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

i didn't have any problem updating. from what you're telling yours is a
linker problem. and fpic should be disabled by default by the profile.
try doing a revdep-rebuild -p and see if it finds something wrong on your
system, then try again updating the lib.
and if you're using the unstable branch of libgdiplus this error may be one
of the problems for which the lib is still in the unstable branch, so wait
some days before updating and retry later.

2007/9/23, agtdino <agtdino@teleline.es>:
>
> After sync I have trouble with libgdiplus any one have some problem ?
>
> ...
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld:
> .libs/image.o: relocation R_X86_64_PC32 against `gdip_getcodecinfo_gif' can
> not be used when making a shared object; recompile with -fPIC
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld:
> final link failed: Bad value
> ...
>
> Thank's and regards
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
dott. ing. beso

[-- Attachment #2: Type: text/html, Size: 1361 bytes --]

  reply	other threads:[~2007-09-23 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-23 15:25 [gentoo-amd64] problem after sync + update libgdiplus agtdino
2007-09-23 17:51 ` Beso [this message]
2007-09-24 18:49   ` Steev Klimaszewski

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=d257c3560709231051o2f3a9391hd94da587a5ccc450@mail.gmail.com \
    --to=givemesugarr@gmail.com \
    --cc=gentoo-amd64@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