Installation fails on Mac OS X 10.6. about bjoern

[gorakhargosh]

I used https://github.com/mxcl/homebrew to install libev. However, my compilation fails for a different reason. Also, macports installs things in /opt/local. Homebrew installs it correctly under /usr/local. I'd advise removing macports and using homebrew instead.

[jonashaag]

GothAlice, would you mind pasting the output of pip when trying to compile bjoern? I'd like to know where pip searches for the headers. I assume ev.h is in /usr/local/include/ev.h?

gorakhargosh, please tell me about your installation problems!

[amcgregor]

http://pastie.textmate.org/private/le7wmzqyavtuajlk7598ww is the output (from ~/.pip/pip.log; waaay too long to paste here).

After a quick search I've determined that libraries are actually installed in /opt/local/include, so the path to ev.h is /opt/local/include/ev.h. I can only guess this is to keep ports installed material away from the rest of the system. :/

[jonashaag]

Humm, no idea how to fix this... this actually seems like a setuptools bug because the libev includes are not included in the gcc call...

[amcgregor]

After symlinking the appropriate libraries and headers from /opt/local/{include,lib} to /usr/local/{include,lib} I've run into a new problem: architecture incompatibility. Now I'm getting some odd errors.

http://pastie.textmate.org/private/4lblopkuhxlkissmzlml0w

[gorakhargosh]

@GothAlice
I'd advise using homebrew. It handles packages on Mac OS X way better than MacPorts. You get the 'just works' tag with it.

[jonashaag]

wtf o_O I have no idea what's going on on your machine, GothAlice... seems like every source file is built three times and for i386, x64 and PPC at the same time. No idea. Weird OS X.

[amcgregor]

Well, it's GCC's default behaviour on 64-bit Mac OS X 10.6 Snow Leopard to compile things for 32-bit, 64-bit, and PPC to create "Universal" binaries.

[jahmad]

afaik by default, macports doesn't build universal binaries. that's the reason of architecture incompability. but that's not a problem since you won't need bjoern to be universal anyway.

i don't know what's the real reason of your compile error, but it definitely is not for the reason mentioned here. i use homebrew on non-standard path, and have no problem compiling bjoern.

what i have: homebrew on /opt/homebrew. CFLAGS="-I/opt/homebrew/include" LDFLAGS="-L/opt/homebrew/lib", and this is the output of pip. http://pastie.textmate.org/1410273

[amcgregor]

Thanks! I'll give homebrew a go when I get a replacement for my failing drive and re-install. If I can avoid macports, I'll be happy, happy girl. ;)

Closing the ticket until I can get a chance to try homebrew out. If I have any additional problems, I'll open a new ticket.

Thank you for all of your excellent and speedy responses. Great support. :)

[jahmad]

i believe it's happened because my english is sucks, please forgive me. but when i said the error definitely is not for any reason mentioned here, i meant macports is included. macports is not the error source.

originally i don't bother to reply since the issue is closed, but after i read the new readme, my guilt is big enough to make me install macports and try to compile bjoern using it.

and yes, i can compile using macports' libev without any problem: http://dpaste.de/wDgd/

again, i'm sorry for the confusion.

[amcgregor]

My computer's HDD failed; with a new installation and tool installation via homebrew (loving it, by the way) I'll give bjoern another try.

[amcgregor]

Let me open a new ticket.