public inbox for gentoo-alt@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Simon <cwrsimon@googlemail.com>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] emerging kde4 apps on Darwin with prefix portage
Date: Fri, 8 Feb 2008 16:46:23 +0100	[thread overview]
Message-ID: <702126C7-D4C3-48E9-8AFA-7929E0382E8F@gmail.com> (raw)
In-Reply-To: <20080208103545.GH1750@gentoo.org>

Am 08.02.2008 um 11:35 schrieb Fabian Groffen:

> On 26-01-2008 20:50:24 +0100, Christian Simon wrote:
> [snip]
>> 6. I failed to emerge soprano (Call stack:
>> *   misc-functions.sh:703: <call install_qa_check>
>> *   misc-functions.sh:368: 		hasq allow_broken_install_names $ 
>> {FEATURES}
>> || \
>> * 			die "invalid install_name found, your application will crash at
>> runtime"
>> )
>
> Maybe this can be fixed.  I'm not familiar with this package.

Well, it appears to be a fairly new package. KDE3 didn't have it. You  
can skip emerging with USE="-semantik-desktop".
The libraries in question that would cause this error message are  
libsoprano_nquadparser.dylib,  
libsoprano_nquadserializer 
.dylib 
,libsoprano_raptorparser 
.dylib 
,libsoprano_raptorserializer.dylib,libsoprano_redlandbackend.dylib.  
Could it be that these are invalid names for dynamic libraries under  
Darwin?


>> 7. So, I emerged kdelibs with: USE="-semantic-desktop" emerge
>> kde-base/kdelibs:kde-4
>> 8. Then, I emerged kde-base/kwrite:kde-4
>> 9. The result of all efforts is this:
>>
>> christian@christian-simons-mac-mini ~ $
>> Gentoo/usr/bin/kwrite.app/Contents/MacOS/kwrite
>> dyld: Library not loaded:
>> /Users/christian/Gentoo/var/tmp/portage/kde-base/kwrite-4.0.0/work/ 
>> kwrite_build/lib/libkdeinit4_kwrite.dylib
>>  Referenced from:
>> /Users/christian/Gentoo/usr/bin/kwrite.app/Contents/MacOS/kwrite
>>  Reason: image not found
>> Trace/BPT trap
>
> Hmmm, weird Portage didn't catch this issue, whereas it should have as
> far as I can see.  Did you by chance disable something?

No, I didn't disable anything. However, I messed with two eclasses  
files. Maybe, I should rather have changed the ebuilds of the files in  
question as you did with dev-cpp/gccxml.

>> At the moment, I'm too tired to work this out. The greatest  
>> obstacle I had
>> to overcome to get this far was cmake. In the end, it's only a  
>> question of
>> sending the right parameters to cmake, I guess.
>
> If I'm not mistaken, I used cmake yesterday to compile some obscure
> utility.  That would mean that it just works?
Yes, you are right! CMake emerges and works perfectly. However, I had  
to set -CMAKE_INSTALL_PREFIX and -DLIB_SUFFIX to appropriate values.  
Otherwise, cmake wouldn't have installed the files in $EPREFIX/var/tmp/ 
portage/PACKAGE_NAME/image. It took me a little to figure that out...

Thanks for your feedback! I think, one can even download some pre- 
built .dmg packages on kde.org. But emerging one's favourite kde4 apps  
would have been so much more fun ;-)
Regards,
Christian

-- 
gentoo-alt@lists.gentoo.org mailing list



  reply	other threads:[~2008-02-08 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26 19:50 [gentoo-alt] emerging kde4 apps on Darwin with prefix portage Christian Simon
2008-02-08 10:35 ` Fabian Groffen
2008-02-08 15:46   ` Christian Simon [this message]
2008-12-06 21:14     ` Fabian Groffen

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=702126C7-D4C3-48E9-8AFA-7929E0382E8F@gmail.com \
    --to=cwrsimon@googlemail.com \
    --cc=gentoo-alt@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