Re: [racket-dev] Build failure on specific PPC systems
Two days ago, James Vega wrote: Since I've generally had more luck using the cgc GC on less mainstream systems, I set the build to use that for PowerPC and let it be in case things changed and it started working. This is a bad idea. There are certain things that are practically impossible with the CGC. Also, if plot is making problems, just disable it. It is likely to be replaced soon with a racket implementation. Even if it isn't, the overall damage from using the CGC is probably higher than not having plot. -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Build failure on specific PPC systems
At Thu, 25 Aug 2011 23:30:38 -0400, James Vega wrote: On Wed, Aug 24, 2011 at 11:31:05PM -0400, Lennart Sorensen wrote: On Wed, Aug 24, 2011 at 10:58:04PM -0400, Lennart Sorensen wrote: On Wed, Aug 24, 2011 at 07:30:07PM -0400, James Vega wrote: Since at least 4.2.4, Racket has been failing to build[0][1] for Debian on G5-based PowerPC systems[2][3]. At the time, the only other PowerPC system that was available within Debian to debug on was a G4-based system[4]. On that system, Racket has been building fine using either the 3m or cgc GC. Of course it also occured to me that the G5 (IBM 970) and the power6+ I am using are 64bit powerpc machines, while the G4 is 32bit I believe. Might matter. Looks like that may be it. Much of the JIT code leverages GNU Lightning, which doesn't appear to support ppc64 yet. Right --- the Racket JIT definitely does not support PPC in 64-bit mode. The Racket PPC JIT is enabled on Linux when `powerpc' is #defined at build time. Is `powerpc' #defined for the 64-bit build, perhaps in addition to `powerpc64'? Or is just `powerpc64' #defined? Thanks, Matthew _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
[racket-dev] Warnings in source code
Hi, I was just looking at the warnings in racket source code after Sam posted the bite size projects threads with the link to the wiki. I can't access http://drdr.racket-lang.org/ (the page just doesn't load) So, I cloned racket, configured it and did a make. I only get two warning on the whole build: gcc -I./.. -I../../../racket/src/racket/gc2/../include -g -O2 -pthread -Wall-c xsrc/place.c -o place.o ../../../racket/src/racket/gc2/../src/place.c: In function ‘place_async_send’: ../../../racket/src/racket/gc2/../src/place.c:2450:14: warning: operation on ‘ch-in’ may be undefined ../../../racket/src/racket/gc2/../src/place.c: In function ‘scheme_place_async_try_receive’: ../../../racket/src/racket/gc2/../src/place.c:2589:17: warning: operation on ‘ch-out’ may be undefined This is with GCC4.5. I will try later GCC4.6 though but I am amazed GCC4.5 only shows two warnings. Well, it's definitely a good sign but I was wondering if I overlooked something. Do I have to enable any components which when compiled will issue some warnings that you want sorted? Cheers, -- PMatos _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Warnings in source code
On Fri, Aug 26, 2011 at 12:21 PM, Paulo J. Matos pa...@matos-sorge.com wrote: Hi, I was just looking at the warnings in racket source code after Sam posted the bite size projects threads with the link to the wiki. I can't access http://drdr.racket-lang.org/ (the page just doesn't load) So, I cloned racket, configured it and did a make. I only get two warning on the whole build: gcc -I./.. -I../../../racket/src/racket/gc2/../include -g -O2 -pthread -Wall -c xsrc/place.c -o place.o ../../../racket/src/racket/gc2/../src/place.c: In function ‘place_async_send’: ../../../racket/src/racket/gc2/../src/place.c:2450:14: warning: operation on ‘ch-in’ may be undefined ../../../racket/src/racket/gc2/../src/place.c: In function ‘scheme_place_async_try_receive’: ../../../racket/src/racket/gc2/../src/place.c:2589:17: warning: operation on ‘ch-out’ may be undefined This is with GCC4.5. Great. It might be helpful to try building with clang as well, as it gives very helpful warning/error messages. The next step is to figure out how to patch that file to remove the warning. I will try later GCC4.6 though but I am amazed GCC4.5 only shows two warnings. Well, it's definitely a good sign but I was wondering if I overlooked something. I don't think so -- the default configuration builds everything. -- sam th sa...@ccs.neu.edu _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Warnings in source code
On 26/08/11 17:28, Sam Tobin-Hochstadt wrote: Great. It might be helpful to try building with clang as well, as it gives very helpful warning/error messages. The next step is to figure out how to patch that file to remove the warning. I will compile with clang and gcc46 and will try to submit a patch fixing these warnings. Will post back in case I get stuck. -- PMatos _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Warnings in source code
There are plenty of warnings when you build under windows. Robby On Fri, Aug 26, 2011 at 11:39 AM, Paulo J. Matos pa...@matos-sorge.com wrote: On 26/08/11 17:28, Sam Tobin-Hochstadt wrote: Great. It might be helpful to try building with clang as well, as it gives very helpful warning/error messages. The next step is to figure out how to patch that file to remove the warning. I will compile with clang and gcc46 and will try to submit a patch fixing these warnings. Will post back in case I get stuck. -- PMatos _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Warnings in source code
On 26/08/11 17:55, Robby Findler wrote: There are plenty of warnings when you build under windows. oh... :-/ If the problem is windows then I don't think I will be able to help since I don't have access to a windows box at home. -- PMatos _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Warnings in source code
On 26/08/11 17:28, Sam Tobin-Hochstadt wrote: Great. It might be helpful to try building with clang as well, as it gives very helpful warning/error messages. The next step is to figure out how to patch that file to remove the warning. I will try later GCC4.6 though but I am amazed GCC4.5 only shows two warnings. Well, it's definitely a good sign but I was wondering if I overlooked something. ok, at least GCC46 finds heaps of warnings that GCC45 doesn't. None major but will get them sorted. -- PMatos _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Warnings in source code
On Fri, Aug 26, 2011 at 11:58 AM, Paulo J. Matos pa...@matos-sorge.com wrote: On 26/08/11 17:55, Robby Findler wrote: There are plenty of warnings when you build under windows. oh... :-/ If the problem is windows then I don't think I will be able to help since I don't have access to a windows box at home. Not to worry! That is a whole separate other problem. Robby _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Possible useful drdr feature?
I've added http://drdr.racket-lang.org/builds/$PUSH/trunk.tgz for the last 100 builds (going forward) It's an archive of the git trunk after running 'make install'. Jay On Thu, Aug 25, 2011 at 3:06 PM, Eli Barzilay e...@barzilay.org wrote: IIUC, after each drdr build, it generates the report pages, and then it dumps the built tree. If so, how about changing it: before the tree is removed, it archives the built files (run `git ls-files -o') and makes the archive available somewhere. If this is done, then I can do the following: 1. Given that drdr is usually very busy, download new build archives to someplace else (like pre.racket-lang.org) 2. Write some script that you'd run with `git pre-build', which would check whether there's a build archive available for your current HEAD. This means that after you've pulled new stuff into your repo, you could just run this command and get a working tree very quickly. 3. Even more: if there's no archive for your HEAD, it could check your origin/master, and if that's part of your current HEAD history (as happens after a `git pull --rebase'), it will still do that. This means that you'd be left with a tree that has compiled results for an older version, but with most uses of `pull --rebase', this means that only files that you've worked on are outdated, so a followup setup would usually be very quick. 4. Of course, that won't help with changes in src, and the script could warn you about that. It also wouldn't help much if you have edits in core files like in the `racket' collection. -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev -- Jay McCarthy j...@cs.byu.edu Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay The glory of God is Intelligence - DC 93 _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Possible useful drdr feature?
Can you also add some quick file that has just the most recently done push number? (Something that I can poll with minimal cost for the drdr machine.) About a minute ago, Jay McCarthy wrote: I've added http://drdr.racket-lang.org/builds/$PUSH/trunk.tgz for the last 100 builds (going forward) It's an archive of the git trunk after running 'make install'. Jay On Thu, Aug 25, 2011 at 3:06 PM, Eli Barzilay e...@barzilay.org wrote: IIUC, after each drdr build, it generates the report pages, and then it dumps the built tree. If so, how about changing it: before the tree is removed, it archives the built files (run `git ls-files -o') and makes the archive available somewhere. If this is done, then I can do the following: 1. Given that drdr is usually very busy, download new build archives to someplace else (like pre.racket-lang.org) 2. Write some script that you'd run with `git pre-build', which would check whether there's a build archive available for your current HEAD. This means that after you've pulled new stuff into your repo, you could just run this command and get a working tree very quickly. 3. Even more: if there's no archive for your HEAD, it could check your origin/master, and if that's part of your current HEAD history (as happens after a `git pull --rebase'), it will still do that. This means that you'd be left with a tree that has compiled results for an older version, but with most uses of `pull --rebase', this means that only files that you've worked on are outdated, so a followup setup would usually be very quick. 4. Of course, that won't help with changes in src, and the script could warn you about that. It also wouldn't help much if you have edits in core files like in the `racket' collection. -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev -- Jay McCarthy j...@cs.byu.edu Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay The glory of God is Intelligence - DC 93 -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Possible useful drdr feature?
If you go to
http://drdr.racket-lang.org/current
then you will get redirected to the current one.
This shell script:
curl -I http://drdr.racket-lang.org/current | grep Location | awk -F/
'{print $2}'
will give just that number... the Racket code would be simple too
Jay
On Fri, Aug 26, 2011 at 2:13 PM, Eli Barzilay e...@barzilay.org wrote:
Can you also add some quick file that has just the most recently done
push number? (Something that I can poll with minimal cost for the
drdr machine.)
About a minute ago, Jay McCarthy wrote:
I've added
http://drdr.racket-lang.org/builds/$PUSH/trunk.tgz
for the last 100 builds (going forward)
It's an archive of the git trunk after running 'make install'.
Jay
On Thu, Aug 25, 2011 at 3:06 PM, Eli Barzilay e...@barzilay.org wrote:
IIUC, after each drdr build, it generates the report pages, and then
it dumps the built tree. If so, how about changing it: before the
tree is removed, it archives the built files (run `git ls-files -o')
and makes the archive available somewhere.
If this is done, then I can do the following:
1. Given that drdr is usually very busy, download new build archives
to someplace else (like pre.racket-lang.org)
2. Write some script that you'd run with `git pre-build', which would
check whether there's a build archive available for your current
HEAD. This means that after you've pulled new stuff into your
repo, you could just run this command and get a working tree very
quickly.
3. Even more: if there's no archive for your HEAD, it could check your
origin/master, and if that's part of your current HEAD history (as
happens after a `git pull --rebase'), it will still do that. This
means that you'd be left with a tree that has compiled results for
an older version, but with most uses of `pull --rebase', this means
that only files that you've worked on are outdated, so a followup
setup would usually be very quick.
4. Of course, that won't help with changes in src, and the script
could warn you about that. It also wouldn't help much if you have
edits in core files like in the `racket' collection.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
--
Jay McCarthy j...@cs.byu.edu
Assistant Professor / Brigham Young University
http://faculty.cs.byu.edu/~jay
The glory of God is Intelligence - DC 93
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
--
Jay McCarthy j...@cs.byu.edu
Assistant Professor / Brigham Young University
http://faculty.cs.byu.edu/~jay
The glory of God is Intelligence - DC 93
_
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] Possible useful drdr feature?
Three minutes ago, Jay McCarthy wrote:
If you go to
http://drdr.racket-lang.org/current
then you will get redirected to the current one.
This shell script:
curl -I http://drdr.racket-lang.org/current | grep Location | awk -F/
'{print $2}'
will give just that number... the Racket code would be simple too
Yeah, that'll work.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
