Re: [racket-dev] [racket] Code compiled for version ~a, not ~a
I've pushed a fix for the problem with forward slashes in PLTCOLLECTS. I haven't been able to provoke problems with version mismatches or `raco link' not working for a tool. Here's what I tried. Environment: git checkout build in c:\matthew\plt 5.1.3 install in c:\Program Files\Racket-5.1.3 a tool in c:\matthew\collects\uucs1410 (handin for my course) no PLTCOLLECTS or raco links, initially Commands: cd c:\matthew\collects c:\matthew\plt\raco link uu-cs1410 c:\matthew\plt\raco setup -D c:\matthew\plt\drracket [ok --- tool works] c:\matthew\plt\raco link -r uu-cs1410 set PLTCOLLECTS=;c:\matthew\collects c:\matthew\plt\raco setup -D c:\matthew\plt\drracket [ok --- tool works] c:\Program Files\Racket-5.1.3\drracket [error message about bad info-cache] c:\Program Files\Racket-5.1.3\raco setup -D c:\Program Files\Racket-5.1.3\drracket [ok - tool works] c:\matthew\plt\drracket [error message about .zo file version] c:\matthew\plt\raco setup -D c:\matthew\plt\drracket [ok --- tool works] [change schver.h to 5.1.3.10 cd c:\matthew\plt\src\worksp build [interrupt at the bootstrapping from source point, to skip the doc build] c:\matthew\plt\raco setup -D c:\matthew\plt\drracket [ok --- tool works] Can you make the version-mismatch problems happen reliably? If so, can you give me step-by-step instructions that might work on my machine? Thanks! _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
[racket-dev] heads-up on gcc-clang switch
FYI: Extracted from an audio mailing list, of possible interest re: Mac compilation; it looks like Apple's switching to clang. In fact, gcc may (already? soon?) be a front end for clang. John Begin forwarded message: From: Kyle Sluder kyle.slu...@gmail.com Date: September 17, 2011 8:58:27 PM PDT To: Paul Davis p...@linuxaudiosystems.com Cc: coreaudio-...@lists.apple.com API coreaudio-...@lists.apple.com Subject: Re: Commandline Tool Chain? ... So while you can invoke clang directly (don't use GCC anymore; it's unsupported) to produce fully functional Mac OS X binaries ... ... smime.p7s Description: S/MIME cryptographic signature _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] heads-up on gcc-clang switch
Apple has already switched to clang, that happened with XCode 4. Previously, they shipped both and old version of GCC (4.2), and a compiler which used the GCC frontend and an LLVM backend. They made this switch because they didn't like the GPL version 3, which recent versions of GCC (and other GNU software) use. There are two different projects for using GCC as a frontend for LLVM, called llvm-gcc and DragonEgg, with the latter being more up-to-date, I believe. There wouldn't be any point in using GCC as a front-end for clang, since clang is just a front-end for LLVM. On Sun, Sep 18, 2011 at 6:28 PM, John Clements cleme...@brinckerhoff.org wrote: FYI: Extracted from an audio mailing list, of possible interest re: Mac compilation; it looks like Apple's switching to clang. In fact, gcc may (already? soon?) be a front end for clang. John Begin forwarded message: From: Kyle Sluder kyle.slu...@gmail.com Date: September 17, 2011 8:58:27 PM PDT To: Paul Davis p...@linuxaudiosystems.com Cc: coreaudio-...@lists.apple.com API coreaudio-...@lists.apple.com Subject: Re: Commandline Tool Chain? ... So while you can invoke clang directly (don't use GCC anymore; it's unsupported) to produce fully functional Mac OS X binaries ... ... _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev -- sam th sa...@ccs.neu.edu _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] heads-up on gcc-clang switch
On Sep 18, 2011, at 3:33 PM, Sam Tobin-Hochstadt wrote: Apple has already switched to clang, that happened with XCode 4. Previously, they shipped both and old version of GCC (4.2), and a compiler which used the GCC frontend and an LLVM backend. They made this switch because they didn't like the GPL version 3, which recent versions of GCC (and other GNU software) use. There are two different projects for using GCC as a frontend for LLVM, called llvm-gcc and DragonEgg, with the latter being more up-to-date, I believe. There wouldn't be any point in using GCC as a front-end for clang, since clang is just a front-end for LLVM. Everything you say makes sense: one other note--AFAICT, XCode 4 is not (yet?) free for platforms other than Lion. John smime.p7s Description: S/MIME cryptographic signature _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
