On Sun, 14 Nov 2010, Frederic Bouvier wrote:
Hi Gene,
- "Gene Buckle" a écrit :
> Ah, sorry to disappoint, but you have to commit to Git first - unlike
> some setups, we haven't engineered a 'compile before publish' system.
> Hence my ensuring I have time to watch Hudson *after* a commit
Do you guys really wanna know how corrupt the character behind FSP is?
The "team" behind the version of Celestia that he sells, is headed by
an individual named "John Bayer". Anyone with a good knowledge of astronomy
will
know that Johann Bayer (b. 1572) was a German lawyer and uranographer, fa
yes now I know ;) thanks to Jester on #flightgear, using gdb and
valgrind he found out what was wrong: hopefully he knows how to correct
the problem too.
So the "problem" comes from the openAL side, and a correct config in
~/.alsoftrc brings back a nice FG windows ready to make tests on the
zk
2010/11/14 Sébastien MARQUE :
>
> so I've created some logs, hoping they could help:
That's all very nice, but you left out the single most important one:
a gdb backtrace :)
--
Csaba/Jester
--
Centralized Desktop Delive
On 14 Nov 2010, at 08:19, Frederic Bouvier wrote:
>> What about offering those with commit rights the ability to trigger
>> builds on their own? That way if they break it, they can fix it and re-start
>> the build. I've enabled the "email the person that broke the build"
>> option, but I don't
Hi all,
I'm used to compile OSG/svn, SG/git and FG/git on a debian sid system
using gcc version 4.4.5 (Debian 4.4.5-7).
I'm facing a segfault problem for two days now (but I couldn't test
before for more than one week). I've tried different solutions as put
away ~/.fgfs/autosave.xml, then ~/.f
Hi Gene,
- "Gene Buckle" a écrit :
> > Ah, sorry to disappoint, but you have to commit to Git first - unlike
> > some setups, we haven't engineered a 'compile before publish' system.
> > Hence my ensuring I have time to watch Hudson *after* a commit, and, for
> > example, make a fix commit
7 matches
Mail list logo
