torcs-users Mailing List for TORCS - The Open Racing Car Simulator

On Monday 31 May 2004 08:40, David Haggett wrote:
> Do I just need to grab the .src.rpm from the 64bit source DVD and
> recompile? =A0 In this context, do I just set the compiler flags with the
> same export commands when I issue the rpmbuild command, or is it more
> involved than this?

Actually, you don't need to answer this.  I figured it couldn't do any harm=
,=20
so I gave it a go, and after installing my home-brewed plib rpm torcs=20
compiled without errors.

Can't say if it worked or not, because I've decided to try to build an RPM=
=20
from the spec files.  If it works, I'll let you know.
=2D-=20

David Haggett

Bernhard,

Thanks for your assistance so far.  You have encouraged me to keep trying.  I 
have a few more questions, if you would be so kind.  Goes a bit off-topic for 
which I apologise (also for being a bit of a newbie).

On Sunday 30 May 2004 21:29, Bernhard Kaindl, Bernhard Kaindl wrote:
> On Sun, 30 May 2004, David Haggett wrote:
> > On Sunday 30 May 2004 12:16, Eric Espie wrote:
> > > May be that's PLIB that should be compiled with the -fPIC flags ?

> I think it cannot break anything else because plib only provided as static
> library(at least on SuSE 9.1), so any other program which uses it has
> the static library already, compiled into the program binary.

Ah, I think I misunderstood then.  I am not a programmer so much of your 
advice goes a little above my head.  Can you explain what I need to do to 
recompile plib with -fPIC in the context of building and installing torcs?

Do I just need to grab the .src.rpm from the 64bit source DVD and recompile?  
In this context, do I just set the compiler flags with the same export 
commands when I issue the rpmbuild command, or is it more involved than this?

> Because plib is a static library, you cannot break
> anying which is already compiled by recompiling plib with -fPIC.
Thankyou - I didn't understand this before.

> Depending if your DRI/GLX driver also fully supports 32-bit mode on the
> 64-bit kernel and X11, you can also just try to insert the 32-bit DVD and
> install this rpm(but it's not the latest version unfortunately).
I did try this but the graphics were messed up a bit (you could see the road 
through the cars).  I guessed it was an issue with the nVidia driver.

> To try a 32-bit compile, you just use -m32 for each gcc call and gcc will
> automatically compile 32-bit and link with the 32-bit libraries (you may
> need to install some 32-bit development packages for this in addition)
Is this an alternative to using -fPIC and recompiling plib, or something I 
might want to do *as well as* using -fPIC and recompiling plib?

-- 
Many thanks again.
David Haggett

On Sun, 30 May 2004, David Haggett wrote:

> On Sunday 30 May 2004 12:16, Eric Espie wrote:
> > May be that's PLIB that should be compiled with the -fPIC flags ?
> 
> Oh, that's a shame. I'm using the version of plib supplied with the distro, 
> and I'm not sure I want to change it in case it breaks anything else.  Never 
> mind.

I think it cannot break anything else because plib only provided as static
library(at least on SuSE 9.1), so any other program which uses it has
the static library already, compiled into the program binary.

The reason why it fails with TORCS is that it seems at TORCS is the first
program which creates dynamically linked libraries by linking the statically
linked plib library into these dynamic libraries on this new architecture.

BTW, it can be be beneficial for TORCS to compile plib with -fPIC even on ix86,
because ix86 CPUs have to "emulate" the position-independentness during execution
and this may slow down the execution of the code a little.

But I don't know what's faster, emulating and or using -fPIC,
it may depend strongly on the specific CPU. But this is a detail.

Because plib is a static library, you cannot break
anying which is already compiled by recompiling plib with -fPIC.

> I'll ask on the suse newsgroup and see if anyone has got around the issue 
> there. Looks like I may have found the reason torcs wasn't included in the 
> 64bit version.

Not really, I don't know of any other 64-bit platform where TORCS has been
tested so far, so it can be seen from conservative view to not include it
for 64-bit architectures without further testing.

Also, 32-bit bit code generally runs very well on AMD64, even most of the
time a few percent faster because the stack and data types are smaller and
so more addresses and data fit into the chaches and can be transferrey in
by any fixed-width data transfer.

Depending if your DRI/GLX driver also fully supports 32-bit mode on the 64-bit
kernel and X11, you can also just try to insert the 32-bit DVD and install
this rpm(but it's not the latest version unfortunately).

To try a 32-bit compile, you just use -m32 for each gcc call and gcc will
automatically compile 32-bit and link with the 32-bit libraries (you may
need to install some 32-bit development packages for this in addition)

> Thanks for the help anyway... brilliant game.  The Win binaries work on the 
> wife's laptop, so I don't have to give it up completely.

Of course you can install a small 32-bit system on AMD64, but of course
this is really only the last resort if no combination is capable of 64-bit.

Bernhard 

On Sunday 30 May 2004 12:16, Eric Espie wrote:
> May be that's PLIB that should be compiled with the -fPIC flags ?

Oh, that's a shame. I'm using the version of plib supplied with the distro, 
and I'm not sure I want to change it in case it breaks anything else.  Never 
mind.

I'll ask on the suse newsgroup and see if anyone has got around the issue 
there. Looks like I may have found the reason torcs wasn't included in the 
64bit version.

Thanks for the help anyway... brilliant game.  The Win binaries work on the 
wife's laptop, so I don't have to give it up completely.
-- 

David Haggett

David Haggett wrote:
> On Sunday 30 May 2004 07:03, Eric Espie wrote:
> 
>>You should use:
>>
>>export CXXFLAGS=-fPIC
>>export CLAGS=-fPIC
> 
> Added 'F' to make this CFLAGS=-fPIC
> 
>>export CPPFLAGS=-fPIC
>>./configure
> 
> 
> Thanks for this, I'm getting a lot further through the compile now, but still 
> fails with the same error.
> 
> c++ -shared -o simuv2.so simu.o simuitf.o car.o aero.o engine.o axle.o steer.o 
> susp.o brake.o wheel.o transmission.o differential.o collide.o categories.o 
> -L/home/david/build/torcs-1.2.2/export/lib  -L/usr/X11R6/lib64 -L/usr/lib   
> -lplibsg -lplibul -L/home/david/build/torcs-1.2.2/export/lib -lsolid
> /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../lib64/libplibsg.a(sg.o): 
> relocation R_X86_64_32S can not be used when making a shared object; 
> recompile with -fPIC
> /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../lib64/libplibsg.a: 
> could not read symbols: Bad value
> collect2: ld returned 1 exit status
> make[5]: *** [simuv2.so] Error 1
> 
> As CFLAGS, CXXFLAGS and CPPFLAGS are all -fPIC, I'm guessing there's another 
> flag to set (but which one?)
> 
> Thanks for help so far.

May be that's PLIB that should be compiled with the -fPIC flags ?

Eric.
-- 
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
               TORCS - http://torcs.org
             The Open Racing Car Simulator
         AKA The Other Release Coming Soon (Skin'r)
            How soon is soon ? (RaceBlizter)
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=

On Sunday 30 May 2004 07:03, Eric Espie wrote:
> You should use:
>
> export CXXFLAGS=-fPIC
> export CLAGS=-fPIC
Added 'F' to make this CFLAGS=-fPIC
> export CPPFLAGS=-fPIC
> ./configure

Thanks for this, I'm getting a lot further through the compile now, but still 
fails with the same error.

c++ -shared -o simuv2.so simu.o simuitf.o car.o aero.o engine.o axle.o steer.o 
susp.o brake.o wheel.o transmission.o differential.o collide.o categories.o 
-L/home/david/build/torcs-1.2.2/export/lib  -L/usr/X11R6/lib64 -L/usr/lib   
-lplibsg -lplibul -L/home/david/build/torcs-1.2.2/export/lib -lsolid
/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../lib64/libplibsg.a(sg.o): 
relocation R_X86_64_32S can not be used when making a shared object; 
recompile with -fPIC
/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../lib64/libplibsg.a: 
could not read symbols: Bad value
collect2: ld returned 1 exit status
make[5]: *** [simuv2.so] Error 1

As CFLAGS, CXXFLAGS and CPPFLAGS are all -fPIC, I'm guessing there's another 
flag to set (but which one?)

Thanks for help so far.
-- 

David Haggett

Thierry Thomas wrote:
> Le Sam 29 mai 04 à 19:05:18 +0200, David Haggett <da...@ha...>
>  écrivait :
> 
>>On Saturday 29 May 2004 14:31, Thierry Thomas wrote:
>>
>>>recompile with -fPIC.
>>>
>>>You can define CPPFLAGS+= -fPIC
>>
>>Thanks for the reply.  You couldn't explain how to do this could you?  Is it 
>>something I can set with an export command?  Should I set it before I run the 
>>configure script, or do I have to append it to the make command?
> 
> 
> This is just a make variable. I have no experience with SuSE, but the
> following command should work:
> 
> make CPPFLAGS=-fPIC

You should use:

export CXXFLAGS=-fPIC
export CLAGS=-fPIC
export CPPFLAGS=-fPIC
./configure
make

because CXXFLAGS is used for the C++ compilations
CFLAGS for the C compilations and CPPFLAGS for
the C-preprocessing (dependencies)

you can also add the target machine as I do:

export CXXFLAGS=-march=i686
export ...
(change it with the corresponding architecture).

Bye,
Eric.
-- 
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
               TORCS - http://torcs.org
             The Open Racing Car Simulator
         AKA The Other Release Coming Soon (Skin'r)
            How soon is soon ? (RaceBlizter)
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=

Le Sam 29 mai 04 =E0 19:05:18 +0200, David Haggett <da...@ha....c=
o.uk>
 =E9crivait=A0:
> On Saturday 29 May 2004 14:31, Thierry Thomas wrote:
> > recompile with -fPIC.
> >
> > You can define CPPFLAGS+=3D -fPIC
>=20
> Thanks for the reply.  You couldn't explain how to do this could you?  =
Is it=20
> something I can set with an export command?  Should I set it before I r=
un the=20
> configure script, or do I have to append it to the make command?

This is just a make variable. I have no experience with SuSE, but the
following command should work:

make CPPFLAGS=3D-fPIC
--=20
Th. Thomas.

On Saturday 29 May 2004 14:31, Thierry Thomas wrote:
> recompile with -fPIC.
>
> You can define CPPFLAGS+= -fPIC

Thanks for the reply.  You couldn't explain how to do this could you?  Is it 
something I can set with an export command?  Should I set it before I run the 
configure script, or do I have to append it to the make command?

Sorry to be so dense.

-- 

David Haggett

Le Sam 29 mai 04 =E0 18:17:22 +0200, be...@bl... <be...@bl...=
>
 =E9crivait=A0:
> >I've got the same problem on FreeBSD / amd64. Just does what it says:
> >recompile with -fPIC.
>=20
> That?s interesting. Does TORCS work then on 64-bit architectures compil=
ed
> as 64 binary (I have no such system to try it myself)?

Unfortunetaly, I have no such system myself. I have just fixed the build
for the FreeBSD compilation farm. Now binary packages should be created,
and if somebody runs one, he might report errors...
--=20
Th. Thomas.

Hi all

>I've got the same problem on FreeBSD / amd64. Just does what it says:
>recompile with -fPIC.

That=B4s interesting. Does TORCS work then on 64-bit architectures compil=
ed
as 64 binary (I have no such system to try it myself)?

bye, Bernhard.
=20

Le Sam 29 mai 04 =E0 14:19:33 +0200, David Haggett <da...@ha....=
uk>
 =E9crivait=A0:
> /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-linux/=
bin/ld:=20
> controlconfig.o: relocation R_X86_64_32 can not be used when making a sha=
red=20
> object; recompile with -fPIC

I've got the same problem on FreeBSD / amd64. Just does what it says:
recompile with -fPIC.

You can define CPPFLAGS+=3D -fPIC.

Regards,
--=20
Th. Thomas.

I was a bit disappointed to find torcs was not included on the 64bit version 
of SUSE 9.1.  The 32bit version installs OK, but the graphics is a bit messed 
up (the cars have holes in them) so I thought I'd have a go at compiling.

The configure script appears to finish without errors (see attached 
torcs-config.out).  However `make' craps out with the following error (see 
also torcs-make.out)

/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-linux/bin/ld: 
controlconfig.o: relocation R_X86_64_32 can not be used when making a shared 
object; recompile with -fPIC

I'm building as a user from a subdirectory of my home directory.  I think I've 
got all the dependencies installed, but I'm not a coder, so I might well be 
missing something obvious.  Is it possible to compile torcs for x86_64?

Also, I notice that the ./configure script creates .spec files.  Is there a 
simple way to use the unpacked sources to create an RPM  (my normal practice 
is to use checkinstall).

-- 
Many thanks in advance

David Haggett

Hi all

Attached you can find my ideas for TORCS championship rules. This is a 
draft intended for discussion and to check if there is any interest at 
all for a championship. So please reply to the torcs-users mailing list 
if you are interested. I release such a rough draft because it is not 
worth to refine it or to set up the infrastructure if there is no interest.

Thank you for you feedback, bye

Bernhard.

-- 

visit my homepage http://www.berniw.org

Hi,
 
I've downloaded both torcs 1.2.1 and 1.2.2 (windows binaries). The 1.2.1 runs perfectly but the 1.2.2 hangs and bombs out on READY! The FAQ suggests I change the display colors to 24 or 36 bpp I've done that but it does not help. the output around the READY! stage is like this
 
=======Begin Output Dump ========
 
 
4 drivers ready to race
Initializing Driver LLiaw...
Initializing Driver Player...
Gear 0: Spd -87.480794
Gear 2: Spd 65.775030
Gear 3: Spd 98.293023
Gear 4: Spd 134.585843
Gear 5: Spd 174.961588
Gear 6: Spd 236.434570
Gear 7: Spd 291.602637
Initializing Driver Tita...
Initializing Driver manulite...
Gear 0: Spd -100.530210
Gear 2: Spd 52.633617
Gear 3: Spd 93.516476
Gear 4: Spd 128.884900
Gear 5: Spd 166.165631
Gear 6: Spd 207.278778
Gear 7: Spd 268.080579
Running Prestart...
Ready.
GfParmReadFile: Openning "config/graph.xml" (056233FC)
initCars: start invalid enumerant
GfParmReadFile: Openning "config/graph.xml" (0562B11C)
Loading data/textures/frontlight1.rgb
Loading data/textures/frontlight2.rgb
Loading data/textures/rearlight1.rgb
Loading data/textures/rearlight2.rgb
Loading data/textures/breaklight1.rgb
Loading data/textures/breaklight2.rgb
Loading drivers/lliaw/logo.rgb
Loading drivers/human/logo.rgb
Loading drivers/tita/logo.rgb
Loading data/textures/logo.rgb
Loading cars/viper-gts-r/shadow.rgb
Loading cars/clkdtm/shadow.rgb
Loading cars/lotus-gt1/shadow.rgb
Loading cars/p406/shadow.rgb
Loading data/textures/rpm8500.rgb
Loading data/textures/speed360.rgb
[gr] Init(0) car viper-gts-r for driver lliaw index 1
Loading cars/viper-gts-r/tex-wheel.rgb
CarLoadAC3D loading viper-gts-r.acc
CarLoadAC3D loading viper-gts-r-lod1.acc
CarLoadAC3D loading viper-gts-r-lod2.acc
[gr] Init(1) car clkdtm for driver human index 1
Loading cars/clkdtm/tex-wheel.rgb
CarLoadAC3D loading clkdtm.acc
CarLoadAC3D loading clkdtm-lod1.acc
CarLoadAC3D loading clkdtm-lod2.acc
[gr] Init(2) car lotus-gt1 for driver tita index 1
Loading cars/lotus-gt1/tex-wheel.rgb
CarLoadAC3D loading lotus-gt1.acc
CarLoadAC3D loading lotus-gt1-lod1.acc
CarLoadAC3D loading lotus-gt1-lod2.acc
Loading data/textures/rpm7000.rgb
Loading data/textures/speed240.rgb
[gr] Init(3) car p406 for driver human index 2
Loading cars/p406/tex-wheel.rgb
CarLoadAC3D loading p406.acc
CarLoadAC3D loading p406-lod1.acc
CarLoadAC3D loading p406-lod2.acc
CarLoadAC3D loading p406-lod3.acc
CarLoadAC3D loading p406-lod4.acc
CarLoadAC3D loading p406-lod5.acc
CarLoadAC3D loading p406-lod6.acc
CarLoadAC3D loading p406-lod7.acc
Loading data/textures/smoke.rgb
Loading data/textures/fire0.rgb
Loading data/textures/fire1.rgb
GfParmWriteFile: config/graph.xml file written
GfParmWriteFile: config/graph.xml file written
 
======End Dump ============
 
I notice the line 
 
initCars: start invalid enumerant
 
in the output. Does anyone know what that means and how i can fix it.
 
Respectfully,
 
Manulite

		
---------------------------------
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs 

hi, im have some troubles with the robots...  when i
configure the playe=
rs just i is in the list...  and this
error message appears in my displa=
y, please how can i
fix this problem?

>>>linuxModInfoDir: ...
>>>/us=
r/local/lib/torcs/drivers/astigot/astigot.so: cannot
>>>open shared obje=
ct file: No such file or directory [2]
>>>linuxModInfoDir: ...
>>>/usr/=
local/lib/torcs/drivers/berniw/berniw.so: cannot
>>>open shared object f=
ile: No such file or directory [2]
>>>linuxModInfoDir: ...
>>>/usr/loca=
l/lib/torcs/drivers/berniw2/berniw2.so: cannot
>>>open shared object fil=
e: No such file or directory


thanks MIKE.

ops...  my email adaptc=
12...@bo..., please help -me!=0A =0A___________________________________=
_______________________________________=0AAcabe com aquelas janelinhas qu=
e pulam na sua tela.=0AAntiPop-up UOL - =C9 gr=E1tis!=0Ahttp://antipopup.=
uol.com.br/=0A

hi, im have some troubles with the robots...  when i
configure the playe=
rs just i is in the list...  and this
error message appears in my displa=
y, please how can i
fix this problem?

>>>linuxModInfoDir: ...
>>>/us=
r/local/lib/torcs/drivers/astigot/astigot.so: cannot
>>>open shared obje=
ct file: No such file or directory [2]
>>>linuxModInfoDir: ...
>>>/usr/=
local/lib/torcs/drivers/berniw/berniw.so: cannot
>>>open shared object f=
ile: No such file or directory [2]
>>>linuxModInfoDir: ...
>>>/usr/loca=
l/lib/torcs/drivers/berniw2/berniw2.so: cannot
>>>open shared object fil=
e: No such file or directory


thanks MIKE.=0A =0A____________________=
______________________________________________________=0AAcabe com aquela=
s janelinhas que pulam na sua tela.=0AAntiPop-up UOL - =C9 gr=E1tis!=0Aht=
tp://antipopup.uol.com.br/=0A