1 |
I tested the new ebuild in the tree, with USE="X cairo foreign |
2 |
(multilib) opengl -backtrace -cgc -doc futures places -plain -profile |
3 |
-sgc -slatex -static" on ~amd64. |
4 |
Worked (compiled) fine. |
5 |
|
6 |
Next I enabled the "backtrace" flag - also worked fine. |
7 |
|
8 |
But when I enabled the "profile" flag, the build hung as per my |
9 |
previous post regarding 5.0.2. (Only it turns out that "profile" was |
10 |
the culprit - the only one of those flags I didn't mention |
11 |
originally.) Last console message was "Compiling xform support... |
12 |
Done making xform-collects." |
13 |
lt-racketcgc taking up 100% CPU. |
14 |
|
15 |
|
16 |
|
17 |
On Tue, Feb 22, 2011 at 2:51 PM, Cyprien Nicolas <c.nicolas@×××××.com> wrote: |
18 |
> Hello lispers, |
19 |
> |
20 |
> I pushed an ebuild for racket-5.1 in the lisp overlay. I updated the |
21 |
> patch, it is needed for plain install to work (i.e. to skip the |
22 |
> compilation of rackets libraries, the long setup-racket phase). |
23 |
> |
24 |
> It has been lightly tested on my stable x86 laptop and stable |
25 |
> amd64-multilib desktop. At least it compiles without failure. |
26 |
> |
27 |
> Here are a few comments and thoughts I want to share: |
28 |
> |
29 |
> * In 5.0.2, I sped up the "raco setup" phase by adding the -j options to |
30 |
> the PLT_SETUP_OPTIONS. I added this to the install-cgc target in 5.1. |
31 |
> |
32 |
> * I renamed the desktop entry from DrScheme to DrRacket, as it's the new |
33 |
> name of the IDE. |
34 |
> |
35 |
> * I removed the build directory, in favor of a build directly in the |
36 |
> source directory. Such use of a build directory is not needed as the |
37 |
> source code is removed after the merge, it avoids unnecessary copying of |
38 |
> files. |
39 |
> |
40 |
> * 'slatex' nor 'static' USE flags have been enabled during my builds, so |
41 |
> it may just work, or not. |
42 |
> |
43 |
> |
44 |
> 1. Does enable cgc (or sgc) should disable the build for 3m? If not, we |
45 |
> could add a default enabled 3m USE for building the 3m-gc-based racket |
46 |
> (currently the default case). It is easy to add this possibility. |
47 |
> I'm fine by just using 3m, I don't know if there is specific users needs. |
48 |
> |
49 |
> 2. A bug has been opened about racket and PaX, but I don't know anything |
50 |
> about PaX, so I'll let somebody else to take care of the bug. |
51 |
> https://bugs.gentoo.org/show_bug.cgi?id=355285 |
52 |
> |
53 |
> 3. If someone has a hint on how to fix/hide the |
54 |
> "configure: WARNING: unrecognized options:"... |
55 |
> I didn't look into it too much yet. |
56 |
> |
57 |
> |
58 |
> Regards |
59 |
> ,Cyprien |
60 |
> |
61 |
> |
62 |
> PS: USE=cgc caused a high memory consumption on my desktop during the |
63 |
> raco setup, one build has even been killed because my system ran out of |
64 |
> memory, so use it with caution, or expect slow downs, if you don't |
65 |
> have/use the autogroup scheduler :) (I don't have a tmpfs PORT_TMPDIR). |
66 |
> |
67 |
> PS2: Thanks to Morgon and Neil for their feedback. and Dimitri for the |
68 |
> initial racket ebuild. |
69 |
> |
70 |
> |
71 |
> On 02/22/2011 08:05 PM, Morgon Kanter wrote: |
72 |
>> Not sure what's different between our systems, but I had both futures |
73 |
>> and places available (though not backtrace) and my build went just |
74 |
>> fine. Actually, my use flags were: X cairo doc foreign futures opengl |
75 |
>> places (everything else was unset). |
76 |
>> |
77 |
>> Some of these flags need documentation. |
78 |
>> |
79 |
>> -- Morgon |
80 |
>> |
81 |
>> On Tue, Feb 22, 2011 at 12:53 PM, Neil Funk <infinitedowntime@×××××.com> wrote: |
82 |
>>>> May I ask you which USE flags combination(s) you tried it with, and on |
83 |
>>>> which arch? |
84 |
>>> |
85 |
>>> I'm on ~amd64. |
86 |
>>> dev-scheme/racket-5.1 was built with the following: |
87 |
>>> USE="X cairo foreign (multilib) opengl -backtrace -cgc -doc -futures |
88 |
>>> -places -plain -profile -sgc -slatex -static" |
89 |
>>> |
90 |
>>> The only other suggestion I'd offer is regarding the backtrace, |
91 |
>>> futures, and places flags. At least on 5.0.2, one or more of these |
92 |
>>> cause the build to hang forever at 100% CPU. Only when I finally gave |
93 |
>>> up and killed the build did I notice the ewarn that these flags can |
94 |
>>> cause that. I realize there's only so much we can protect people from |
95 |
>>> themselves, but it would have been nice if it made me acknowledge that |
96 |
>>> I intended to use a risky flag. Ideally, we'd just fix whatever |
97 |
>>> causes it to hang, but that's an upstream issue - could we maybe just |
98 |
>>> mask those flags? Although, I haven't tested them on 5.1 yet to see |
99 |
>>> if they're even still a problem... |
100 |
>>> |
101 |
>>> Cyprien, I'd be happy to help test with other configurations. Thanks |
102 |
>>> for your work. |
103 |
>>> |
104 |
>>> -Neil |
105 |
>>> |
106 |
>>> On Tue, Feb 22, 2011 at 5:32 AM, Cyprien Nicolas <c.nicolas@×××××.com> wrote: |
107 |
>>>> On 21/02/11 18:07, Morgon Kanter wrote: |
108 |
>>>>> Hey folks, |
109 |
>>>>> |
110 |
>>>>> I noticed there wasn't yet an ebuild for the new version of Racket, so |
111 |
>>>>> I went ahead and made one. It's attached. |
112 |
>>>>> |
113 |
>>>>> A couple changes besides just bumping the version number: |
114 |
>>>>> * Doesn't really seem like that makefile patch was required anymore (I |
115 |
>>>>> didn't need it), so I commented that out. |
116 |
>>>>> * The new Racket GUI system doesn't appear to include any of those |
117 |
>>>>> external libraries that the ebuild used to issue an "rm" for, so I |
118 |
>>>>> removed those bits from the ebuild (as well as the formerly |
119 |
>>>>> commented-out rm commands that were replaced by something different). |
120 |
>>>>> |
121 |
>>>>> That's it for the changes, aside from a version bump. |
122 |
>>>>> |
123 |
>>>>> Thanks, |
124 |
>>>>> -- Morgon |
125 |
>>>> |
126 |
>>>> Actually, there is a work-in-progress ebuild, but I didn't had the time |
127 |
>>>> to test it intensively, especially with the cgc and sgc garbage |
128 |
>>>> collectors, and the plain USE flags (as the makefile patch is related to |
129 |
>>>> those USEs), and I just it an "emake failed" with USE=plain. |
130 |
>>>> |
131 |
>>>> Apart from some cosmetic changes (EAPI4, REAUIRED_USE="cgc? ( !sgc )", |
132 |
>>>> some spacing) my ebuild is the same :) |
133 |
>>>> |
134 |
>>>> May I ask you which USE flags combination(s) you tried it with, and on |
135 |
>>>> which arch? (applies for Neil too). |
136 |
>>>> Thanks for the feedback |
137 |
>>>> |
138 |
>>>> Regards |
139 |
>>>> |
140 |
>>>> ,Cyprien |
141 |
>>>> |
142 |
>>>> |
143 |
>>> |
144 |
> |
145 |
> |