On Fri, Mar 23, 2007 at 01:32:14PM +0100, Peter Dyballa wrote:
> Hello!
>
> While making GTK 2.6.10 this warning is repeated often:
>
> Making all in pixops
> libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
Yup...it's apparently a literal string comparison, so
/sw/lib//libintl.la isn't "the same as" /sw/lib/libintl.la. Humans
know it's the same meaning, so the warning can be safely ignored. No
clue why libtool constructs the .la pathname that way sometimes, since
the makefiles and linker flags all look normal. I asked pogma about
this pathname issue a while back and he shrugged.
dan
--
Daniel Macks
dmacks@...
http://www.netspace.org/~dmacks

Hello!
While making GTK 2.6.10 this warning is repeated often:
Making all in pixops
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
Making all in x11
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
Making all in xdgmime
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
Making all in input
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
Making all in pixbuf
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
Making all in gdk-pixbuf-xlib
libtool: link: warning: `/sw/lib//libintl.la' seems to be moved
--
Package manager version: 0.27.1
Distribution version: 0.8.1.rsync powerpc
Mac OS X version: 10.4.9
Xcode version: 2.4.1
gcc version: 4.0.1 (Apple Computer, Inc. build 5367)
make version: 3.79.1
Feedback Courtesy of FinkCommander
--
Greetings
Pete
There are two major products that come out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence.
- Jeremy S. Anderson

On 3/13/07, Oliver Polden <oliver.polden@...> wrote:
> ./configure: line 2495: syntax error near unexpected token `0.35.0'
> ./configure: line 2495: `IT_PROG_INTLTOOL(0.35.0)'
this is at least a slightly more enlightening error than we saw previously...
What's in configure, line 2495 in
/sw/src/fink.build/libbonobo2-2.16.0-1/libbonobo-2.16.0 ?

Am 10.03.2007 um 14:03 schrieb Martin Costabel:
>
>>> I get 1.10.1. Maybe your pkg-config is not Fink's /sw/bin/pkg-=20
>>> config?
>> pkg-config --debug --print-errors --exists --print-errors "pango =20
>> >=3D 1.8.0" reveals:
>
> And the same with pangoxft instead of pango?
Trying ``pkg-config --print-errors --exists 'pangoxft >=3D 1.2.0'=B4=B4 =
I get:
Package pangoxft was not found in the pkg-config search path.
Perhaps you should add the directory containing `pangoxft.pc'
to the PKG_CONFIG_PATH environment variable
No package 'pangoxft' found
because I had removed the pango1-xft2-ft219 packages before. The only =20=
pangoxft.pc file was: /sw/lib/pango-ft219/lib/pkgconfig/pangoxft.pc. =20
OK, now that the auxiliary files in /usr/X11R6 were the original =20
versions, I removed, re-built, and re-installed the general pango1-=20
xft2 packages. And configure finished successfully and compilation =20
has started! (And the xserver branch of X11R7.1 finally was updated =20
in CVS so it could be compiled too, hopefully!)
Thank you all!
--
Greetings
Pete
"There's no place like 127.0.0.1"
origin unknown

Peter Dyballa wrote:
[]
>> /usr/X11R6/bin/freetype-config is provided by whatever X11 package
>> you've installed, and is not a symlink to anything. Did you modify
>> yours?
>
> I did so, to make a lot of applications use Fink's Freetype. Undoing
> my change, configure still fails:
>
> checking for x86 platform... no
> checking for freetype-config... /usr/X11R6/bin/freetype-config
> checking For sufficiently new FreeType (at least 2.0.1)... yes
> configure: error: Xft Pango backend is required for x11 target
> ### execution of ./configure failed, exit code 1
It would be useful to see what config.log says about the cause of this
error. The test executed by configure is
if $PKG_CONFIG --exists 'pangoxft >= 1.2.0'
What do you get from
pkg-config --modversion pangoxft
I get 1.10.1. Maybe your pkg-config is not Fink's /sw/bin/pkg-config?
[]
> Trying to remove the "general" pango1-xft2 packages Fink tries to re-
> install them:
>
> The package 'pango1-xft2' will be installed.
> Reading dependency for pango1-xft2-1.10.1-1003...
> The package 'pango1-xft2-dev' will be installed.
> Reading dependency for pango1-xft2-dev-1.10.1-1003...
> The package 'pango1-xft2-shlibs' will be installed.
> Reading dependency for pango1-xft2-shlibs-1.10.1-1003...
> The following 3 packages will be rebuilt:
> gtk+2 gtk+2-dev gtk+2-shlibs
> The following 3 additional packages will be installed:
> pango1-xft2 pango1-xft2-dev pango1-xft2-shlibs
This as a result of a "fink remove" command? Strange...
> The specific pango1-xft2-ft219 packages were installed today as a try
> to enable installation of GTK+2.
Perhaps because you had made bold symlinks to some ft-219 stuff? Here I
can remove all the pango1-xft2-ft219* packages and then rebuild gtk+2,
without any pango1-xft2-ft219 package being reinstalled.
--
Martin

Hi there,
maybe it is related to my X11 configuration or a bug somewhere in
bundle-gnome. i am not sure.
I have set "switch to workspace on the right" in gnome keybindings to
the sequence "control+alt+right arrow" successfully. But it doesn't
work. If I try the sequence "control+alt+a" (for example) it works
perfectly.
any clue ?