-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/5/10 3:36 PM, Łukasz Kucharski wrote:
> 
> 
> W dniu 05.06.10 21:27, Alexander Hansen pisze:
> On 6/5/10 3:05 PM, Aukasz Kucharski wrote:
>>>> I know that -shlibs is the reason that kde would need to be removed too,
>>>> due to deps.
> 
> I make no assumptions about what people know or don't know.
> 
>> Haha, nothing personal. I just thought it was obvious since I've posted 
>> that remove -shlib with recursive end with removing kde. Nevermind me. 
>> It's not relevant =).
> 
>>>> I just though that there might reside some tools that are
>>>> older or broken.
> 
> That could potentially happen, but only if the package shows up as
> linking libraries that are already installed.
> 
>>>>
>>>> Console output i get lines something like:
>>>> g++-4.2 -c -pipe -g -I/sw/lib/system-openssl/include /* cut */
>>>> -I../../../mkspecs/darwin-g++42 -I. -I. -I. -Icpp -I. -I../../../include
>>>> -I../../../include/QtCore -I../../../include/QtXml -I../../xml -o
>>>> .obj/release-shared/uic.o uic.cpp
>>>> c++ -lglib-2.0 -Wl,-dead_strip_dylibs -prebind -o ../../../bin/uic
>>>> .obj/release-shared/customwidgetsinfo.o
>>>> .obj/release-shared/databaseinfo.o .obj/release-shared/driver.o
>>>> .obj/release-shared/treewalker.o .obj/release-shared/ui4.o
>>>> .obj/release-shared/validator.o .obj/release-shared/cppextractimages.o
>>>> .obj/release-shared/cppwritedeclaration.o
>>>> .obj/release-shared/cppwriteicondata.o
>>>> .obj/release-shared/cppwriteicondeclar
>>>>
>>>>
>>>> I believe XCode uses some kind of old gcc version released by apple.
>>>>
>>>> g++-4.2 -v says it's gcc version 4.2.1 (Apple Inc. build 5566)
>>>> and ... c++ -v says it's gcc version 4.3.4 (GCC)
>>>>
>>>> Strange. Could it be my fault ? Like misconfiguration of some kind ?
>>>> Also from what I can see is that most of things are compiled with
>>>> g++-4.2 and the c++ is used like a linker. There is no source codes
>>>> passed as arguments. But that's just from a brief look. Also why would
>>>> 'moc' end with segfault because of the compiler.
>>>>
>>>> Thanks for the assistance, with regards,
>>>>    luk32.
>>>>
> 
> Your c++ looks wrong for Fink build purposes, in any case.  What do you
> get from
> 
> which c++
> 
> and
> 
> $ ls -l `which c++`
> 
> ?
> 
>> luk32mac:~ luk32$ which c++
>> /opt/local/bin/c++
>> luk32mac:~ luk32$ ls -l `which c++`
>> lrwxr-xr-x  1 root  admin  25 Aug 31  2009 /opt/local/bin/c++ -> 
>> /opt/local/bin/c++-mp-4.3
>> luk32mac:~ luk32$ /opt/local/bin/c++-mp-4.3 -v
>> [cut]
>> gcc version 4.3.4 (GCC)
> 
>> Well seems like not Xcode related stuff.
> 
>>

That could well be why your build is failing.  You have a Macports c++
at the head of your PATH.  Fink assumes that builds are using Xcode, or
possibly compiler tools that _it_ installed.

We can confirm whether this is the "c++" that Fink is using by running
"fink dumpinfo -e PATH qt4-x11".  If /opt/local/bin is in the PATH that
fink is using, that could be problematic.

fink doesn't use any user-level environment customizations, in an
attempt to avoid problems.  I'm not sure how Macports sets up its
environment, but you may need to deactivate that for any shell session
while you build Fink packages.

If /opt/local/bin isn't in the PATH you get from the dumpinfo, then a
little more thought is needed
- --
Alexander Hansen
Fink User Liaison
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwKr44ACgkQB8UpO3rKjQ+jlgCgoQRzLSL+BczvQEh76uH0pMnt
8YIAoJxaQ2RdyzyvGWRAu3vF5rWWeGe3
=vaJW
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to