1 |
On Wed, Sep 12, 2012 at 4:57 PM, Alan McKinnon <alan.mckinnon@×××××.com>wrote: |
2 |
|
3 |
> On Wed, 12 Sep 2012 11:15:25 -0400 |
4 |
> Michael Mol <mikemol@×××××.com> wrote: |
5 |
> |
6 |
> > On Wed, Sep 12, 2012 at 10:55 AM, Alan McKinnon |
7 |
> > <alan.mckinnon@×××××.com>wrote: |
8 |
> > |
9 |
> > > On Wed, 12 Sep 2012 16:00:34 +0200 |
10 |
> > > Alex Schuster <wonko@×××××××××.org> wrote: |
11 |
> > > |
12 |
> > > > Michael Mol writes: |
13 |
> > > > |
14 |
> > > > > On Wed, Sep 12, 2012 at 9:33 AM, Neil Bothwick |
15 |
> > > > > <neil@××××××××××.uk <mailto:neil@××××××××××.uk>> wrote: |
16 |
> > > > |
17 |
> > > > > Instead we get, try USE="-*" :P |
18 |
> > > > > |
19 |
> > > > > "Try MAKEOPTS='-j1'" |
20 |
> > > > |
21 |
> > > > Which in fact often helps... especially for me, I am using |
22 |
> > > > MAKEOPTS="-j --load=4", and I often experience build problems that |
23 |
> > > > are not reproducible with a fixed number of jobs, regardless how |
24 |
> > > > large. |
25 |
> > > |
26 |
> > > Yes indeed, and that one is good advice. |
27 |
> > > |
28 |
> > > Not every Makefile out there is safe for -j > 1, so running it as |
29 |
> > > one job is valid debugging. It's the correct thing to do with weird |
30 |
> > > build failures as it tests if a specific condition is true or not. |
31 |
> > > |
32 |
> > > |
33 |
> > Yeah, except I've already gone that route, or otherwise ruled it out, |
34 |
> > before I ask. That's why it's grating. (Even more grating when I have |
35 |
> > to spend the time building a package again, just to convince someone |
36 |
> > that, no, it's not MAKEOPTS that's the problem.) |
37 |
> > |
38 |
> > It's like "Have you tried turning it off and back on again". |
39 |
> |
40 |
> I learned that one the hard way :-) |
41 |
> |
42 |
> Now when I submit support posts, I try emulate what bgo asks: |
43 |
> |
44 |
> 1. nature of problem |
45 |
> 2. what have I tried already |
46 |
> 3. steps to reproduce |
47 |
> 4. result gotten |
48 |
> 5. expected result |
49 |
> 6. relevant config files and settings |
50 |
> |
51 |
> Tends to weed out a lot of the silly auto-bot style answers |
52 |
> |
53 |
> |
54 |
I'm going through one on launchpad right now where I indicated that I |
55 |
couldn't get beeps out of xterm, but I could get sound from sound-emitting |
56 |
websites. (Trying to get x11 bell to function via PulseAudio via work |
57 |
laptop) |
58 |
|
59 |
First response? "Needs information: Can you get sound from other sound |
60 |
apps?" |
61 |
|
62 |
#pulseaudio simply ignored me. And googling turns up that Lennart hates the |
63 |
X server as being a funnel for sound events. I was physically twitching by |
64 |
the time I gave up... |
65 |
|
66 |
-- |
67 |
:wq |