[Stackless] Re: MacOS build errors...

[Bob Ippolito]

You should use the configure line that I specified:

../configure --enable-framework --with-framework-name=Stackless

And you should do it from a temporary build folder.. I use _framework  
for a release framework build.



On Apr 17, 2004, at 11:16 PM, Damian Jurd wrote:

> Sorry Bob, which directory should I be in then...and are the options  
> I'm passing
> OK?
> to-wit: --enable-toolbox-glue --enable-shared --enable-framework
> --with-framework-name=Stackless
>
> Regards,
> D.
>
> Quoting Bob Ippolito <bob at redivi.com>:
>
>> DO NOT run configure/make from the Mac directory!!
>>
>>
>> On Apr 17, 2004, at 7:12 PM, Damian Jurd wrote:
>>
>>> Bob, here's what it did:
>>>
>>> stackless/src/Mac$ ../configure --enable-toolbox-glue --enable-shared
>>> --enable-framework --with-framework-name=Stackless
>>>
>>> when the configure completed I did a "make" and a "sudo make
>>> frameworkinstall"
>>> in the same directory ("stackless/src/Mac" relative to the CVS
>>> checkout.)
>>>
>>> I also tried using the build script in the  
>>> "stackless/src/Mac/OSX/Dist"
>>> subdirectory with the same result.
>>>
>>> ...(time passes)...
>>>
>>> After considering your message and you original post (in which you
>>> refer to a
>>> "dev" directory?) I thought I'd try it from the
>>> "stackless/src/Stackless"
>>> directory too, but that fails with the same error.
>>>
>>> So in short what directory should I be in? And should I issue the
>>> "configure",
>>> "make", and "sudo make frameworkinstall" in different directories.
>>>
>>> Any help you can give at this point would be greatly appeciated as  
>>> I'm
>>> dying to
>>> get this to work.
>>> D.
>>>
>>> Quoting Bob Ippolito <bob at redivi.com>:
>>>
>>>> Where are you running make frameworkinstall from??
>>>>
>>>> On Apr 16, 2004, at 7:19 PM, Damian Jurd wrote:
>>>>
>>>>> All,
>>>>>
>>>>> I tried building again today with a fresh cvs update and I'm still
>>>>> getting the
>>>>> same error.
>>>>>
>>>>> Bob do you have any thought on why this is happening?
>>>>>
>>>>> during the "make frameworkinstall" portion of the build I get:
>>>>>
>>>>> ...
>>>>> ./python.exe
>>>>> /Users/dnj/build/stackless.com_cvs_update_200404181045_UTC/ 
>>>>> stackless/
>>>>> src/Mac/OSX/Dist/../../../Mac/scripts/cachersrc.py
>>>>> -v
>>>>> /tmp/_py/install/Library/Frameworks/Python.framework/Versions/2.3/
>>>>> lib/
>>>>> python2.3/plat-mac
>>>>> /tmp/_py/install/Library/Frameworks/Python.framework/Versions/2.3/
>>>>> Mac/
>>>>> Tools
>>>>> Traceback (most recent call last):
>>>>>   File
>>>>> "/Users/dnj/build/stackless.com_cvs_update_200404181045_UTC/
>>>>> stackless/
>>>>> src/Mac/OSX/Dist/../../../Mac/scripts/cachersrc.py",
>>>>> line 7, in ?
>>>>>     import macresource
>>>>>   File
>>>>> "/Users/dnj/build/stackless.com_cvs_update_200404181045_UTC/
>>>>> stackless/
>>>>> src/Lib/plat-mac/macresource.py",
>>>>> line 3, in ?
>>>>>     from Carbon import Res
>>>>>   File
>>>>> "/Users/dnj/build/stackless.com_cvs_update_200404181045_UTC/
>>>>> stackless/
>>>>> src/Lib/plat-mac/Carbon/Res.py",
>>>>> line 4, in ?
>>>>>     from _Res import *
>>>>> ImportError: No module named _Res
>>>>> make[1]: *** [installmacsubtree] Error 1
>>>>> make: *** [frameworkinstallmaclib] Error 2
>>>>> ...
>>>>>
>>>>> Quoting Damian Jurd <stackless at drinkinglizard.com>:
>>>>>
>>>>>> I tried building according to Bob's instructions but it fails  
>>>>>> during
>>>>>> install,
>>>>>> I
>>>>>> tried using two different cvs checkouts, one from the 7th and one
>>>>>> from the
>>>>>> 13th. Here's how I built:
>>>>>>
>>>>>> Starbug:~/build/stackless.com_cvs_update_200404130800_UTC/ 
>>>>>> stackless/
>>>>>> src/Mac
>>>>>> dnj$
>>>>>> ../configure --enable-toolbox-glue --enable-shared
>>>>>> --enable-framework
>>>>>> --with-framework-name=Stackless
>>>>>>
>>>>>> ...I'm on a freshly built Panther box, the error output was:
>>>>>>
>>>>>> ./python.exe ../Mac/scripts/cachersrc.py -v
>>>>>> /Library/Frameworks/Stackless.framework/Versions/2.3/lib/ 
>>>>>> python2.3/
>>>>>> plat-mac
>>>>>> /Library/Frameworks/Stackless.framework/Versions/2.3/Mac/Tools
>>>>>> Traceback (most recent call last):
>>>>>>   File "../Mac/scripts/cachersrc.py", line 7, in ?
>>>>>>     import macresource
>>>>>>   File
>>>>>>
>>>>> "/Users/dnj/build/stackless.com_cvs_update_200404130800_UTC/
>>>>> stackless/
>>>>> src/Lib/plat-mac/macresource.py",
>>>>>> line 3, in ?
>>>>>>     from Carbon import Res
>>>>>>   File
>>>>>>
>>>>> "/Users/dnj/build/stackless.com_cvs_update_200404130800_UTC/
>>>>> stackless/
>>>>> src/Lib/plat-mac/Carbon/Res.py",
>>>>>> line 4, in ?
>>>>>>     from _Res import *
>>>>>> ImportError: No module named _Res
>>>>>> make[1]: *** [installmacsubtree] Error 1
>>>>>> make: *** [frameworkinstallmaclib] Error 2
>>>>>>
>>>>>> ...any thoughts?
>>>>>>
>>>>>> D.
>>>>>>
>>>>>> ps. Sorry to all for my previous multiple posts...loose nut on the
>>>>>> keyboard
>>>>>> ;-)
>>>>>>
>>>>>> Quoting Bob Ippolito <bob at redivi.com>:
>>>>>>
>>>>>>>
>>>>>>> On Apr 8, 2004, at 1:57 PM, Damian Jurd wrote:
>>>>>>>
>>>>>>>> I've seen Bob's comment in a previous post saying that you
>>>>>>>> shouldn't
>>>>>>>> install a
>>>>>>>> 2nd copy of Python under Panther. So how can I safely get a copy
>>>>>>>> of
>>>>>>>> stackless
>>>>>>>> running under python? Should I pass some extra stuff to the
>>>>>>>> configure
>>>>>>>> script?
>>>>>>>> Does this mean that it can't/shouldn't be built as a framework?
>>>>>>>
>>>>>>>  From the dev tree..
>>>>>>> ../configure --enable-framework --with-framework-name=Stackless
>>>>>>> make
>>>>>>> sudo make frameworkinstall
>>>>>>>
>>>>>>> Note that this will make /usr/local/bin/python*, but the  
>>>>>>> framework
>>>>>>> will
>>>>>>> be /Library/Frameworks/Stackless.framework.  I personally just rm
>>>>>>> -rf
>>>>>>> /usr/local/bin/python* after a make frameworkinstall, and then I
>>>>>>> have a
>>>>>>> symlink named stackless that points at
>>>>>>> /Library/Frameworks/Stackless.framework/Versions/2.3/Resources/
>>>>>>> Stackless.app/Contents/MacOS/Stackless.
>>>>>>>
>>>>>>> Let me know if you have problems, there are probably things I  
>>>>>>> have
>>>>>>> overlooked.  If it were ready to be a nice supported  
>>>>>>> self-contained
>>>>>>> thing on OS X, I would already be distributing it ;)
>>>>>>>
>>>>>>> -bob
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
> _______________________________________________
> Stackless mailing list
> Stackless at stackless.com
> http://www.stackless.com/mailman/listinfo/stackless


_______________________________________________
Stackless mailing list
Stackless at stackless.com
http://www.stackless.com/mailman/listinfo/stackless