Holger Wirtz wrote:
> I don't understand why there is this problem... is this a bug in the
> fglrx_dri.so? Why does fgfs worked until this problem occurs a month ago?
>
> I tried to use the ATI drivers from www.ati.com, but they have no DRI
> driver for Radeon X1400 Chips :-(
fglrx *is* the dri
Hi,
On Wed, Jul 11, 2007 at 02:55:44PM +0200, Csaba Halász wrote:
> On 7/11/07, John Denker <[EMAIL PROTECTED]> wrote:
> > On 07/10/2007 01:40 PM, Csaba Halász wrote:
> >
> > > Maybe try the sed hack with a shorter prefix, such as replacing
> > > _ZNSt6vector with _ZNSt6vectorX. Note that it is a
On 7/11/07, John Denker <[EMAIL PROTECTED]> wrote:
> On 07/10/2007 01:40 PM, Csaba Halász wrote:
>
> > Maybe try the sed hack with a shorter prefix, such as replacing
> > _ZNSt6vector with _ZNSt6vectorX. Note that it is a pretty brutal thing
> > to do for the whole binary, and might break it in a m
On 07/10/2007 01:40 PM, Csaba Halász wrote:
> Maybe try the sed hack with a shorter prefix, such as replacing
> _ZNSt6vector with _ZNSt6vectorX. Note that it is a pretty brutal thing
> to do for the whole binary, and might break it in a million ways.
1) It's more likely to work if the replacement
Hi Csaba,
On Tue, Jul 10, 2007 at 07:40:46PM +0200, Csaba Halász wrote:
> Hi Holger!
>
> Maybe try the sed hack with a shorter prefix, such as replacing
> _ZNSt6vector with _ZNSt6vectorX. Note that it is a pretty brutal thing
> to do for the whole binary, and might break it in a million ways. Or,
Hi Holger!
Maybe try the sed hack with a shorter prefix, such as replacing
_ZNSt6vector with _ZNSt6vectorX. Note that it is a pretty brutal thing
to do for the whole binary, and might break it in a million ways. Or,
set LD_DEBUG=bindings and LD_OUTPUT as appropriate. Then run fg, and
try to find s
Hi,
On Tue, Jul 10, 2007 at 01:58:36AM +0200, Csaba Halász wrote:
> On 7/9/07, Holger Wirtz <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > sorry for reanimating this thread, but since a week I have the old
> > problem regardless using the "sed"-hack to
> > /usr/lib/dri/fglrx_dri.so. :-(
> >
> > Does a
On 7/9/07, Holger Wirtz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> sorry for reanimating this thread, but since a week I have the old
> problem regardless using the "sed"-hack to
> /usr/lib/dri/fglrx_dri.so. :-(
>
> Does anyone know what I can do or what is needed for debugging?
For a start, please prov
Hi,
sorry for reanimating this thread, but since a week I have the old
problem regardless using the "sed"-hack to
/usr/lib/dri/fglrx_dri.so. :-(
Does anyone know what I can do or what is needed for debugging?
Thanks, Holger
On Tue, Jun 19, 2007 at 11:22:30AM +0200, Holger Wirtz wrote:
> Hi all,
Hi all,
On Sun, Jun 17, 2007 at 07:37:41PM -0400, John Denker wrote:
[...]
> 2) Here is another way of achieving a similar result. This is more
> crude, but works better in batch files, i.e. doesn't require any
> skilled feedback. This works for 32- and 64-bit libraries.
>
> sed s/_ZNSt6vecto
There
On 06/17/2007 06:04 PM, Martin Spott wrote:
> You might want to give Pigeon a copy of your hacked driver for
> use with the FGLive CD,
We have discovered that there are multiple versions of
"the" driver. This means it is not easy to distribute
hacked copies or even to distribute a patch.
"Csaba Halász" wrote:
> Yesterday we seem to have successfully hacked the fglrx_dri.so. You
> can ask ndim or Jester (me) on irc for 32 bit and 64 bit patched
> versions respectively.
You might want to give Pigeon a copy of your hacked driver for
use with the FGLive CD,
Martin.
--
Unix
John Denker wrote:
> On 06/16/2007 05:25 PM, Martin Spott wrote:
> >
> > Ah, ok. Simply compile OSG from source and install just by "make
> > install" - this definitely works well, at least on Etch,
>
> How "definitely" is that?
I've been compiling OSG SVN on Etch for months now. In fact
On 6/17/07, John Denker <[EMAIL PROTECTED]> wrote:
>
> This is observed with recent (a few hours old) versions of
> osg-2.0, simgear, plib, and fg.
>
> This is observed with a variety of aircraft, including
> the default c172p, the c182r, and the pa24-250.
>
> First example (abort):
>
> #0 0xb74e7
On 06/17/2007 09:45 AM, I wrote:
> 100% of the CPU for 2.3 billion CPU clock cycles,
Correction: make that 140 billion CPU clock cycles.
(I left out a factor of 60 seconds/minute. Sorry.)
-
This SF.net email is sponsored
Ron Jensen wrote:
>> Thanks, but the problem is in OSG. I have been building and installing
>> debian packages. Its not the supported way to build, so when it quit
>> working I didn't complain.
On 06/16/2007 05:25 PM, Martin Spott wrote:
>
> Ah, ok. Simply compile OSG from source and install j
Ron Jensen wrote:
> On Sat, 2007-06-16 at 10:37 +, Martin Spott wrote:
> > This is everuthing I need to build FG with current OSG,
> >
>
> Thanks, but the problem is in OSG. I have been building and installing
> debian packages. Its not the supported way to build, so when it quit
> working
On Sat, 2007-06-16 at 10:37 +, Martin Spott wrote:
> Ron Jensen wrote:
>
> > I must agree. I haven't had a working flightgear for about a month
> > because OSG-SVN/head quit building for me.
>
> How does the error message look like ? I know, unfortunately I'm
> repeating myself, yet it mig
Nick Warne wrote:
> I have been building OSG over the last 3 months, and even updated today to
> rev. 7002 - everything builds/works great and I haven't had to touch a
> thing!?
Perhaps you've been building against old OSG headers. Few weeks ago
Robert Osfield has removed a header file that con
On Saturday 16 June 2007 11:37:35 Martin Spott wrote:
> Ron Jensen wrote:
> > I must agree. I haven't had a working flightgear for about a month
> > because OSG-SVN/head quit building for me.
>
> How does the error message look like ? I know, unfortunately I'm
> repeating myself, yet it might help
Ron Jensen wrote:
> I must agree. I haven't had a working flightgear for about a month
> because OSG-SVN/head quit building for me.
How does the error message look like ? I know, unfortunately I'm
repeating myself, yet it might help applying this patch to FlightGear:
--- FlightGear/src/Main/f
"Curtis Olson" wrote:
> Our approach with plib is that if we absolutely must depend on something in
> cvs, we push the plib folks hard to get that into an official release first,
> then we cut over and allow our code to depend on it. This is not without
> headaches, but it's worked pretty well fo
Jonathan Wagner wrote:
> Just a thought for the rest of the list. Now that OpenSceneGraph-2.0
> has been released, what are the thoughts on setting that as a "fixed"
> dependency for now (i.e., future development should work on
> OpenSceneGraph-2.0).
While we are at it, somebody could now add
On Fri, 2007-06-15 at 19:33 -0500, Curtis Olson wrote:
> On 6/15/07, Jonathan Wagner wrote:
> Just a thought for the rest of the list. Now that
> OpenSceneGraph-2.0
> has been released, what are the thoughts on setting that as a
> "fixed"
> dependency for no
On 6/15/07, Jonathan Wagner wrote:
Just a thought for the rest of the list. Now that OpenSceneGraph-2.0
has been released, what are the thoughts on setting that as a "fixed"
dependency for now (i.e., future development should work on
OpenSceneGraph-2.0). With one of the latest patches to the p
Just a thought for the rest of the list. Now that OpenSceneGraph-2.0
has been released, what are the thoughts on setting that as a "fixed"
dependency for now (i.e., future development should work on
OpenSceneGraph-2.0). With one of the latest patches to the plib branch
in CVS, FlightGear stil
26 matches
Mail list logo
