Your right !

I needed, for an other application, to set this command :

$ defaults write com.apple.versioner.python Prefer-32-Bit -bool yes

At this point, I know the problem, I'll resolve it

Many Thanks !

-- 
Nicolas Alex Michel

On 21 juin 2012, at 10:47, Abdulla Kamar wrote:

> Have you installed your own version of Python? It's a little odd that the 
> system framework doesn't have x86_64 support.
> 
> On Thu, Jun 21, 2012 at 6:26 PM, Michel Nicolas Alex 
> <[email protected]> wrote:
> Hi All
> 
> As I try to install Inkscape, I got an error with boost1.46.1.cmake-shlibs.
> I already launched common things like :
> 
> $> fink scanpackages
> $> sudo apt-get update
> $> fink selfupdate
> 
> Any idea ?
> 
> Thanks !
> 
> 
> 
> $> fink install boost1.46.1.cmake-shlibs
> 
> [skip]
> /sw/src/fink.build/boost1.46.1.cmake-1.46.1-1/pocb-boost-a8aa807/boost/python/detail/make_tuple.hpp:14:5:
>  note: instantiated from:
>    PyTuple_SET_ITEM(                                   \
>    ^
> /usr/include/python2.5/tupleobject.h:52:37: note: instantiated from:
> #define PyTuple_SET_ITEM(op, i, v) (((PyTupleObject *)(op))->ob_item[i] = v)
>                                    ^
> /usr/include/python2.5/tupleobject.h:26:5: note: array 'ob_item' declared here
>    PyObject *ob_item[1];
>    ^
> 22 warnings generated.
> Linking CXX shared library ../../../lib/libboost_python-mt.dylib
> ld: warning: ignoring file /Library/Frameworks//Python.framework/Python, file 
> was built for unsupported file format which is not the architecture being 
> linked (x86_64)
> Undefined symbols for architecture x86_64:
>  "_PyString_FromStringAndSize", referenced from:
>      boost::python::numeric::(anonymous namespace)::load(bool) in 
> numeric.cpp.o
>      boost::python::detail::str_base::str_base(char const*, char const*) in 
> str.cpp.o
>      boost::python::detail::str_base::str_base(char const*, char const*) in 
> str.cpp.o
>      boost::python::detail::str_base::str_base(char const*, unsigned long) in 
> str.cpp.o
>      boost::python::detail::str_base::str_base(char const*, unsigned long) in 
> str.cpp.o
>      boost::python::converter::do_return_to_python(char) in 
> builtin_converters.cpp.o
>      boost::python::tuple boost::python::make_tuple<boost::python::str, 
> boost::python::api::object, boost::python::str, boost::python::str, 
> boost::python::str, std::string>(boost::python::str const&, 
> boost::python::api::object const&, boost::python::str const&, 
> boost::python::str const&, boost::python::str const&, std::string const&) in 
> function_doc_signature.cpp.o
>      ...
> [skip]
>  "_PyRun_StringFlags", referenced from:
>      boost::python::eval(boost::python::str, boost::python::api::object, 
> boost::python::api::object) in exec.cpp.o
>      boost::python::exec(boost::python::str, boost::python::api::object, 
> boost::python::api::object) in exec.cpp.o
>      boost::python::exec_statement(boost::python::str, 
> boost::python::api::object, boost::python::api::object) in exec.cpp.o
>  "_PyFile_FromString", referenced from:
>      boost::python::exec_file(boost::python::str, boost::python::api::object, 
> boost::python::api::object) in exec.cpp.o
>  "_PyFile_AsFile", referenced from:
>      boost::python::exec_file(boost::python::str, boost::python::api::object, 
> boost::python::api::object) in exec.cpp.o
>  "_PyRun_FileExFlags", referenced from:
>      boost::python::exec_file(boost::python::str, boost::python::api::object, 
> boost::python::api::object) in exec.cpp.o
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> make[2]: *** [lib/libboost_python-mt.1.46.1.dylib] Error 1
> make[1]: *** [libs/python/src/CMakeFiles/boost_python-mt-shared.dir/all] 
> Error 2
> make: *** [all] Error 2
> ### execution of /tmp/fink.vQ2hi failed, exit code 2
> ### execution of /tmp/fink.pDfFC failed, exit code 2
> Removing runtime build-lock...
> Removing build-lock package...
> /sw/bin/dpkg-lockwait -r fink-buildlock-boost1.46.1.cmake-1.46.1-1
> (Lecture de la base de données... 41085 fichiers et répertoires déjà 
> installés.)
> Suppression de fink-buildlock-boost1.46.1.cmake-1.46.1-1 ...
> Failed: phase compiling: boost1.46.1.cmake-1.46.1-1 failed
> 
> Before reporting any errors, please run "fink selfupdate" and try again.
> 
> If you continue to have issues, please check to see if the FAQ on Fink's
> website solves the problem.  If not, ask on one (not both, please) of
> these mailing lists:
> 
>        The Fink Users List <[email protected]>
>        The Fink Beginners List <[email protected]>,
> 
> with a carbon copy to the maintainer:
> 
>        Abdulla Kamar <[email protected]>
> 
> Note that this is preferable to emailing just the maintainer directly,
> since most fink package maintainers do not have access to all possible
> hardware and software configurations.
> 
> Please try to include the complete error message in your report.  This
> generally consists of a compiler line starting with e.g. "gcc" or "g++"
> followed by the actual error output from the compiler.
> 
> Also include the following system information:
> Package manager version: 0.33.2
> Distribution version: selfupdate-rsync Thu Jun 21 09:34:14 2012, 10.7, x86_64
> Trees: local/main stable/main stable/crypto unstable/main unstable/crypto
> Xcode.app: 4.2.1
> Xcode command-line tools: 4.2.1
> Max. Fink build jobs:  1
> [skip]
> 
> 
> 
> --
> Nicolas Alex Michel
> 


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fink-beginners mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.beginners
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to