Ken Thomases, Ben Kennedy,
thanks for the replies!
Yes, I tried "libpython33.so", "libpython33.dylib", "python33.dylib", ...
But I still get that error, even if the file is "ls -al":
-r-xr-xr-x@ 1 ecir staff 5503912 29 sep 10:27 libpython33.so
That "-v" switch is a good advice but I cannot really make any sense of
this http://pastebin.com/ugWxEWw8
On Sun, Feb 24, 2013 at 9:51 PM, Ken Thomases <k...@codeweavers.com> wrote:
> On Feb 24, 2013, at 2:09 PM, ecir hana wrote:
>
> > and running "file python33" says:
> >
> > python33 (for architecture i386): Mach-O dynamically linked shared
> > library i386
> > python33 (for architecture x86_64): Mach-O 64-bit dynamically linked
> > shared library x86_64
> >
> > The problem I have is that when try to run:
> >
> > "gcc embed.c -I./include -L. -lpython33"
> >
> > if breaks with:
> >
> > ld: library not found for -lpython33
> >
> > Please, does anyone know why?
>
> The -l option expects a file with the prefix "lib" and a library suffix.
> So, -lpython33 requires that the file be named libpython33.<something>
> (where something might be dylib or a or possibly a couple of other things).
>
> When you have issues like this, you might try passing -v for verbose
> output. It would probably tell you precisely which file names it tried.
>
> Regards,
> Ken
>
>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
