Re: [Chicken-users] chicken hangs and uses 100% cpu (mac os x lion)

[Topher Cyll]

Thanks, everyone!

Switching compilers fixed the build for me.

I've attached a patch to fix the build in this configuration.  It's
very conservative and only selects gcc-4.2 if the OS is Mac OS X Lion
and gcc-4.2 is available.

I've done my best to follow the existing pattern of config-arch.sh.  I
also did my best to keep the config-macosx-compiler.sh script POSIX sh
compatible.

I know working around this bug may not be ideal, though.  Is a patch
like this appropriate to go into git?

Topher




On Tue, Sep 13, 2011 at 9:02 PM, Kon Lovett <address@hidden> wrote:
> This might be relevant - was for me:
>
> http://lists.nongnu.org/archive/html/chicken-users/2011-08/msg00005.html
>
> But what is actually the problem would be good to know.
>
> On Sep 13, 2011, at 5:56 PM, Topher Cyll wrote:
>
>> Hey everyone,
>>
>> Like a previous poster, I'm having issues with Chicken on Mac OS X
>> (although for me the issues are on Lion, not Snow Leopard).
>>
>> I started building from MacPorts (4.4.0) and had the same issue as the
>> previous poster.  The build succeeds, but trying to run csc or csi
>> results in what appears to be an infinite loop (no output and 100% cpu
>> usage).
>>
>> Since then, I've built from the source releases for: 4.7.0, 4.6.0,
>> 4.5.0, 4.4.0, 4.3.0, 4.2.0, 4.1.0, and 4.0.0.  All of them build
>> correctly, but when I run "install", the process hangs on
>> "chicken-install -update-db" and cpu usage goes to 100% again.
>>
>> I've also tried building from HomeBrew (4.7.0) and it also hangs while
>> updating the db.
>>
>> Am I right that chicken-install is executing code written in chicken?
>> I'm not completely positive this is the same problem, but it seems
>> likely.
>>
>> Also, I'm not sure I did this right, but I tried to do a system trace
>> using Instruments (which ships with XCode).  I was hoping for a
>> smoking gun, but all I see is this repeated over and over again:
>>
>> BSC_sigprocmask
>> BSC_sigreturn
>>
>> Not sure how to interpret that, although it seems like something
>> involving signal handlers might be unhappy?
>>
>> Anyone else bumped into this?  I'm happy to try to figure out what's
>> going on if anyone has any suggestions.  Is there any way to build a
>> debug version of chicken?
>>
>> Thanks everyone,
>> Topher
>>
>> _______________________________________________
>> Chicken-users mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/chicken-users
>
>

macosx-lion-gcc-build.patch
Description: Binary data