failed to build dia
normen.mueller at googlemail.com
Mon Sep 29 04:09:36 PDT 2008
Ryan Schmidt wrote:
> On Sep 29, 2008, at 05:53, Normen Müller wrote:
>> Ryan Schmidt wrote:
>>> On Sep 29, 2008, at 04:44, Normen Müller wrote:
>>>> I am trying to install dia, but get the following error:
>>>> # port install dia
>>>> ---> Fetching gtk2
>>>> Error: Some libs are missing from your X11 installation. Please run
>>>> this command:
>>>> Error: sudo ln -s libXrandr.2.dylib /usr/X11/lib/libXrandr.2.0.0.dylib
>>>> Error: Target org.macports.fetch returned: missing
>>> So it needs the file "libXrandr.2.0.0.dylib".
>>>> Error: The following dependencies failed to build: gtk2 libart_lgpl
>>>> Error: Status 1 encountered during processing.
>>>> However, at /usr/X11/lib there exist the following respective libs:
>>>> # ls -al /usr/X11/lib/libXrandr.*
>>>> lrwxr-xr-x 1 root wheel 17 Aug 4 21:18
>>>> /usr/X11/lib/libXrandr.2.1.0.dylib -> libXrandr.2.dylib
>>>> -rwxr-xr-x 1 root wheel 164144 Mar 5 2008
>>>> lrwxr-xr-x 1 root wheel 17 Feb 21 2008
>>>> /usr/X11/lib/libXrandr.dylib -> libXrandr.2.dylib
>>>> -rwxr-xr-x 1 root wheel 955 May 10 11:41
>>> So you don't have the file "libXrandr.2.0.0.dylib".
>>>> BTW, aren't the parameter order of 'ln' in ``Error: sudo ln -s
>>>> libXrandr.2.dylib /usr/X11/lib/libXrandr.2.0.0.dylib'' wrong?
>>> Looks exactly correct to me. The command says "Create a symlink at
>>> /usr/X11/lib/libXrandr.2.0.0.dylib that points to libXrandr.2.dylib
>>> in the same directory." And that's exactly what you want to do. You
>>> should run the command, like it says.
>> man ln says
>> ln [-Ffhinsv] source_file [target_file]
>> but if I run ``sudo ln -s libXrandr.2.dylib
>> /usr/X11/lib/libXrandr.2.0.0.dylib'' from my home there exists no
> It doesn't look for a file libXrandr.2.dylib in the current working
> directory while you're making the symlink. Rather, it looks for a file
> libXrandr.2.dylib in the directory where the symlink is, which is
>> Anyway, I will delete the first of the following two links, but leave
>> the second one.
>> /usr/X11/lib/libXrandr.2.0.0.dylib -> /usr/X11/lib/libXrandr.2.dylib
>> /usr/X11/lib/libXrandr.2.1.0.dylib -> libXrandr.2.dylib
> You can delete the libXrandr.2.0.0.dylib symlink if you like, and
> re-create it as per the originally given command. Or you can leave it;
> it's not hurting anything that you put the full pathname into the symlink.
You are absolutely right. I removed my link and re-created with
$ sudo ln -s libXrandr.2.dylib /usr/X11/lib/libXrandr.2.0.0.dylib
and the result is:
# ls -al /usr/X11/lib/libXrandr.*
/usr/X11/lib/libXrandr.2.0.0.dylib -> libXrandr.2.dylib
/usr/X11/lib/libXrandr.2.1.0.dylib -> libXrandr.2.dylib
/usr/X11/lib/libXrandr.dylib -> libXrandr.2.dylib
>> Eventually, that means we have to wait for bug fix, right?
> The libXrandr.2.0.0.dylib issue is completely fixed by creating the
> symlink as above.
> However, the missing _jas_whatever symbols from your second message is a
> mystery to me so someone with knowledge of gtk and jasper will have to
> look into that. I'm hoping Anthony will have some idea, or know where to
> ask for help.
Alright, I will wait ;-)
Thanks for your help, anyway!
More information about the macports-users