On Sat, 2010-02-06 at 23:02 +, leee wrote:
> On Saturday 06 Feb 2010, Martin Spott wrote:
> > leee wrote:
> > > On Saturday 06 Feb 2010, Martin Spott wrote:
> > >> John Denker wrote:
> > >> > The fact that workarounds exist for this bug seems to
> > >> > be rather strong evidence that the bug e
leee wrote:
> John's 'Joe' the non-C++ programmer is a valid scenario. Implying
> that the problem only occurs when people don't understand the
> implications of what they're doing is like suggesting that people
> who can't do their own automobile maintenance and repairs shouldn't
> drive, or in
On Saturday 06 Feb 2010, Martin Spott wrote:
> leee wrote:
> > On Saturday 06 Feb 2010, Martin Spott wrote:
> >> John Denker wrote:
> >> > The fact that workarounds exist for this bug seems to
> >> > be rather strong evidence that the bug exists.
> >>
> >> The sole fact that you're getting in troub
leee wrote:
> On Saturday 06 Feb 2010, Martin Spott wrote:
>> John Denker wrote:
>> > The fact that workarounds exist for this bug seems to
>> > be rather strong evidence that the bug exists.
>>
>> The sole fact that you're getting in trouble with the way you are
>> doing things on your very local
John Denker wrote:
> No, that is not the bug I am reporting.
> Beware that the word "linker" is ambiguous. ld is
> different from ld.so. More precisely, /usr/bin/ld
> is different from /lib/libdl.so* ... different
> program, different purpose, different specifications.
>
> For example, I can c
On Sat, 6 Feb 2010 07:57:40 -0600, Curtis wrote in message
:
> On Sat, Feb 6, 2010 at 4:29 AM, Erik Hofman wrote:
>
> > [ the "model view".]
> >
> > I never understood this view anyhow, what is it supposed to do?
>
>
> As I recall, the point of this view was to show an external view of
> the a
On Sat, Feb 6, 2010 at 8:49 PM, Curtis Olson wrote:
> On Sat, Feb 6, 2010 at 1:39 PM, Csaba Halász wrote:
>>
>> On native 64 bits systems there is no point in having a separate /lib
>> and /lib64 - I certainly don't see any. Debian does provide the
>> symlinks as I said.
>
> You can't ever think o
On Saturday 06 Feb 2010, Martin Spott wrote:
> John Denker wrote:
> > The fact that workarounds exist for this bug seems to
> > be rather strong evidence that the bug exists.
>
> The sole fact that you're getting in trouble with the way you are
> doing things on your very local setup doesn't prove
On Sat, Feb 6, 2010 at 8:39 PM, Csaba Halász wrote:
> On Sat, Feb 6, 2010 at 5:17 PM, Tim Moore wrote:
> >
> > On Sat, Feb 6, 2010 at 4:18 PM, John Denker wrote:
> >>
> >> On 02/06/2010 07:54 AM, Csaba Halász wrote:
> >>
> >> > On 64 bit systems /lib64 should really be a symlink to /lib (simila
On Sat, Feb 6, 2010 at 1:39 PM, Csaba Halász wrote:
>
> On native 64 bits systems there is no point in having a separate /lib
> and /lib64 - I certainly don't see any. Debian does provide the
> symlinks as I said.
>
You can't ever think of a situation where you might need 64 bit and 32 bit
versio
On Sat, Feb 6, 2010 at 5:17 PM, Tim Moore wrote:
>
> On Sat, Feb 6, 2010 at 4:18 PM, John Denker wrote:
>>
>> On 02/06/2010 07:54 AM, Csaba Halász wrote:
>>
>> > On 64 bit systems /lib64 should really be a symlink to /lib (similarly
>> > for /usr/lib64) as that is the native architecture.
>> > I
There is something lurking in the tile cache manager ... I haven't seen it
in a while, but there's something there that breaks once in a while.
Curt.
On Sat, Feb 6, 2010 at 9:45 AM, S Andreason wrote:
> Curtis Olson wrote:
> > I have no idea why the scenery would show up different in this view
On Sat, Feb 6, 2010 at 4:18 PM, John Denker wrote:
> On 02/06/2010 07:54 AM, Csaba Halász wrote:
>
> > On 64 bit systems /lib64 should really be a symlink to /lib (similarly
> > for /usr/lib64) as that is the native architecture.
> > I say copy the stuff from lib64 to lib and create the symlink.
John Denker wrote:
> The fact that workarounds exist for this bug seems to
> be rather strong evidence that the bug exists.
The sole fact that you're getting in trouble with the way you are
doing things on your very local setup doesn't prove a single bug,
Martin.
--
Unix _IS_ user fri
On 02/06/2010 08:06 AM, Erik Hofman wrote:
>> That does not fix the main problem. It does not fix
>> the bug that I am reporting.
>
> The problem you reported is that the linker can't locate the library.
> If it's location is defined in ld.so.conf (and after running ldconfig)
> it can.
No, tha
Curtis Olson wrote:
> I have no idea why the scenery would show up different in this view
> for John ... maybe more issues of our code not being 100% compatible
> with ATI hardware (or visa versa?)
>
It is not just the model view. All views _afterward_ are also missing
the nearby scenery, and I
On Sat, Feb 6, 2010 at 9:06 AM, Erik Hofman wrote:
> The problem you reported is that the linker can't locate the library.
> If it's location is defined in ld.so.conf (and after running ldconfig)
> it can.
There is a big difference between the compiler finding the library at
compile time and the
On 02/06/2010 07:54 AM, Csaba Halász wrote:
> On 64 bit systems /lib64 should really be a symlink to /lib (similarly
> for /usr/lib64) as that is the native architecture.
> I say copy the stuff from lib64 to lib and create the symlink.
That is one way of doing it.
By my count there are at least
John Denker wrote:
> On 02/06/2010 02:32 AM, Erik Hofman wrote:
>
>> As I see it this might actually be a problem for the Linux vendor. They
>> should have added /usr/lib64 to /etc/ld.so.conf
>
> That does not fix the main problem. It does not fix
> the bug that I am reporting.
The problem you
On Fri, Feb 5, 2010 at 11:05 PM, John Denker wrote:
> On 02/05/2010 02:38 PM, Curtis Olson wrote:
>> I don't doubt that there could be some lib vs. lib64 inconsistencies, but
>> FilghtGear builds right out of the box for me on 64bit Fedora 12 ... no
>> hitches at all that I recall and it has done
On 02/06/2010 02:32 AM, Erik Hofman wrote:
> As I see it this might actually be a problem for the Linux vendor. They
> should have added /usr/lib64 to /etc/ld.so.conf
That does not fix the main problem. It does not fix
the bug that I am reporting.
ld.so.conf is meaningful at runtime. The prob
Heiko Schulz wrote:
> When I read this I could remember that X-Plane uses something similar.
>
> And yep, it seems so:
>
> http://scenery.x-plane.com/library.php?doc=about_facades.php
> http://scenery.x-plane.com/library.php?doc=facspec.php
>
> Just as an idea and for discussion
Very inte
Anders Gidenstam wrote:
> On Sat, 6 Feb 2010, Erik Hofman wrote:
>
>> Does this mean this view option only works properly when the mutiplayer
>> option is selected? If so the I guess the option should be disabled by
>> default and only bge available when MP is active.
>
> No, for me it seems to b
On Saturday 06 February 2010 12:15:15 pm Jon Stockill wrote:
> Curtis Olson wrote:
> > I don't doubt that there could be some lib vs. lib64 inconsistencies,
> > but FilghtGear builds right out of the box for me on 64bit Fedora 12 ...
> > no hitches at all that I recall and it has done so for quite
Hi,
On Tuesday 02 February 2010 05:46:45 pm Dick Maurer wrote:
> I know there's a problem with dc3-04.rgb I've got to resolve that one.
>
> Maybe somebody can import the update into CVS.
>
>
I tried getting your changed into CVS, but decided to hold back on committing
after I found a few errors.
On Sat, 6 Feb 2010, Erik Hofman wrote:
> Does this mean this view option only works properly when the mutiplayer
> option is selected? If so the I guess the option should be disabled by
> default and only bge available when MP is active.
No, for me it seems to behave perfectly ok also without MP
On Sat, Feb 6, 2010 at 4:29 AM, Erik Hofman wrote:
> [ the "model view".]
>
> I never understood this view anyhow, what is it supposed to do?
As I recall, the point of this view was to show an external view of the
aircraft from a fixed heading. For some situations and some people, all the
extra
Gijs de Rooy wrote:
> > Erik wrote:
> > I never understood this view (model-view) anyhow, what is it supposed
> to do?
>
> In the bottomleft corner of your screen a "dialog" shows up, that allows
> you to
> cycle through helicopter-views from yourself and the other MP pilots.
Does this mean t
Curtis Olson wrote:
> I don't doubt that there could be some lib vs. lib64 inconsistencies,
> but FilghtGear builds right out of the box for me on 64bit Fedora 12 ...
> no hitches at all that I recall and it has done so for quite some time.
Same for me on slackware64.
Jon
-
> Erik wrote:
> I never understood this view (model-view) anyhow, what is it supposed to do?
In the bottomleft corner of your screen a "dialog" shows up, that allows you to
cycle through helicopter-views from yourself and the other MP pilots.
Quite a nice feature to view other's landings!
Chee
John Denker wrote:
> Here’s the setup: Start the program as
>
> fgfs --airport=KLXV --metar=" 012345Z 0KT 99SM CLR 15/M01 A2992"
>
> Let the aircraft sit on the runway. There is no need to start the engine. Use
> the "v" key to cycle through the available views. The scenery looks norm
First of all, I don't think that Jpoe the Plumber should or will compile
FlightGear him/herself. Anybody who wants to do so should learn how to
do that.
John Denker wrote:
> Another workaround -- the one I actually prefer -- is to
> let OSG live under .../lib64/ but add
>
>LDFLAGS="$LD
32 matches
Mail list logo
