On 7 Nov 2011, at 12:04, Quentin Mathé wrote: > Hi, > > To compile LanguageKit, I had to work around the glibc __block issue in > various places once again. > The patch is pretty ugly, so before committing it I wanted to know if someone > had a better solution.
The same better solution I've suggested the last four times you've encountered this problem: $ cat unistd.h #ifdef __block # undef __block # include_next "unistd.h" # define __block __attribute__((__blocks__(byref))) #else # include_next "unistd.h" #endif Just drop this file into any directory that has problem (or install it in Local/Library/Headers) and never think about it again. > I tested various examples from the Compiler/Examples directory, and they run > fine. However test.st doesn't work, I get: > > edlc -f test.st > 2011-11-07 13:00:59.907 edlc[9986] ERROR: Can not determine type for sqrt > 2011-11-07 13:00:59.909 edlc[9986] ERROR: Can not determine type for fdim > 2011-11-07 13:00:59.909 edlc[9986] ERROR: Can not determine type for fdim > 2011-11-07 13:00:59.909 edlc[9986] ERROR: Can not determine type for putchar > 2011-11-07 13:00:59.909 edlc[9986] ERROR: Can not determine type for putchar > 2011-11-07 13:00:59.909 edlc[9986] ERROR: Can not determine type for putchar > 2011-11-07 13:00:59.911 edlc[9986] Failed to compile input. If you don't have SourceCodeKit installed, this test won't work. > I also ran the test suite. Various Smalltalk tests related to the interpreter > fail, but the JIT tests pass in most cases except: There are a few bugs in the interpreter. Most of the core stuff works, but it needs a bit of work before the release. > - TestRetainOnlyOnce (may be it's an excepted failure…) Please delete your test directory and svn up. This test doesn't exist in svn anymore... > - TestTimesRepeat (removed from the output below, because it never ends) I could reproduce this, but then I updated LanguageKit and it was gone. Are you using LK trunk? > For the record, I'm on Ubuntu 10.4 x86-32. Should be fine. x86-64 and LanguageKit aren't best friends yet, but x86-32 should not have any problems. > In addition, all EtoileFoundation tests pass with the current libobjc2 from > trunk and Clang 3.0 rc 1. Shiny. It sounds like there are no clang or libobjc2 bugs I need to worry about, but there are still some LK ones. David -- Sent from my Difference Engine _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
