I noticed that gcc 4.4 is required for compilation. I know that Mac likes
to tweak gcc. Does this mean that llvm-g++-4.2 is too old? I could install
the normal version of gcc4.6 which is the latest in macports.

On Sun, Nov 27, 2011 at 4:00 PM, Jesse Berwald <[email protected]> wrote:

> Thank you. I too have very little experience with Mac's multiple
> architecture concept. (This would have been done days ago in Linux. argh!)
> Sadly, the plot thickens. After including the two -arch flags and running
> configure, the compiler gets tripped up immediately. It appears that
> multiple architectures are not supports with many compiler options(?):
>
> make  all-recursive
> Making all in src
> Making all in graph
> Making all in centrality
>   CXX    graph_betweenness.lo
> llvm-g++-4.2: -E, -S, -save-temps and -M options are not allowed with
> multiple -arch flags
> make[4]: *** [graph_betweenness.lo] Error 1
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all-recursive] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Jesse
>
> On Sun, Nov 27, 2011 at 3:44 PM, Tiago Peixoto [via Main discussion list
> for the graph-tool project] <[email protected]>wrote:
>
>> > ImportError:
>> dlopen(/usr/local/lib/python2.7/site-packages/graph_tool/libgraph_tool_core.so,
>> 9): no suitable image found.  Did find:
>> >
>> /usr/local/lib/python2.7/site-packages/graph_tool/libgraph_tool_core.so:
>> mach-o, but wrong architecture
>> >
>> >>>>>>>>
>> >
>> > These architecture issues on Mac are mystifying to me. How can
>> > something be built for the wrong architecture if I just compiled it
>> > for that architecture? sigh... Thanks any help you can provide.
>>
>> I have very little experience with building stuff with multiple
>> architectures with apple's GCC, but according to the documentation you
>> should pass something like "-arch i386 -arch x86_64" to the compiler to
>> generate "universal" binaries. From the ./configure command you sent in
>> the first email, it did not seem you passed this. Hence you should try
>> something like:
>>
>>     ./configure CXXFLAGS="-arch i386 -arch x86_64 -I/opt/local/include"
>> <..your other options..>
>>
>> I hope it helps.
>>
>> Cheers,
>> Tiago
>>
>> --
>> Tiago de Paula Peixoto <[hidden 
>> email]<http://user/SendEmail.jtp?type=node&node=3540762&i=0>>
>>
>>
>>
>> _______________________________________________
>> graph-tool mailing list
>> [hidden email] <http://user/SendEmail.jtp?type=node&node=3540762&i=1>
>> http://lists.skewed.de/mailman/listinfo/graph-tool
>>
>> *signature.asc* (566 bytes) Download 
>> Attachment<http://attachment/3540762/0/signature.asc>
>>  --
>> Tiago de Paula Peixoto <[email protected]>
>>
>>
>> ------------------------------
>>  If you reply to this email, your message will be added to the
>> discussion below:
>>
>> http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/boost-errors-building-on-Mac-OSX-tp3540332p3540762.html
>>  To unsubscribe from boost errors building on Mac OSX, click 
>> here<http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3540332&code=amJlcndhbGRAZ21haWwuY29tfDM1NDAzMzJ8MjE1NDAwNjg=>
>> .
>> NAML<http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.InstantMailNamespace&breadcrumbs=instant+emails%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>


--
View this message in context: 
http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/boost-errors-building-on-Mac-OSX-tp3540332p3540816.html
Sent from the Main discussion list for the graph-tool project mailing list 
archive at Nabble.com.
_______________________________________________
graph-tool mailing list
[email protected]
http://lists.skewed.de/mailman/listinfo/graph-tool

Reply via email to