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

Oooooh thanks for theses advices (on analogue device), I will try it this
evening :-)

I myself try to stay on the track most of the time but on certain tracks
like Ruudskogen, it's merely difficult, and when you are completely stopped
1 or 2 times during a race, you can imagine that you have mainly lost the
opportunity to be in the 3 first places at the end of the race.

best regards


2013/11/20 Bernhard Wymann <be...@bl...>

> Hi Arnaud
>
>  When a car skids by rolling on the sidetrack (grass), it begins to skid
>>
>> in every direction and finally systematically turns backwards (in the
>> opposite direction of the race).
>> The fact taht a car skids on the grasssounds rather normalto me, but why
>>
>> is never occasionally ends up facing the trackdirection?
>>
>> Is there an algorithm somewhere that always moves the car in reverse
>> when the car is doing a few slew round ?
>>
>
> No, not at all, during testing I had never that impression, but I try to
> spend most of the time on track, with varying success;-) Non the less, a
> slight (tiny) bias against some moving (not track) direction would be at
> least thinkable because of the center of gravity, driven wheels, etc.
>
> If you have an analogue steering device (mouse, pad or wheel), you can
> usually catch the car with countersteering immediately, or locking the
> wheels up (brakes) until almost 360° of the spin are over, then unlock the
> brakes and catch it. Going neutral or disengage the clutch helps as well.
>
> Kind regards
>
> Bernhard
>
>


-- 
*Arnaud Ceyrolle*

Hi Arnaud

> When a car skids by rolling on the sidetrack (grass), it begins to skid
> in every direction and finally systematically turns backwards (in the
> opposite direction of the race).
> The fact taht a car skids on the grasssounds rather normalto me, but why
> is never occasionally ends up facing the trackdirection?
>
> Is there an algorithm somewhere that always moves the car in reverse
> when the car is doing a few slew round ?

No, not at all, during testing I had never that impression, but I try to 
spend most of the time on track, with varying success;-) Non the less, a 
slight (tiny) bias against some moving (not track) direction would be at 
least thinkable because of the center of gravity, driven wheels, etc.

If you have an analogue steering device (mouse, pad or wheel), you can 
usually catch the car with countersteering immediately, or locking the 
wheels up (brakes) until almost 360° of the spin are over, then unlock 
the brakes and catch it. Going neutral or disengage the clutch helps as 
well.

Kind regards

Bernhard

Hello all,

I am happy to notice the new 1.3.5 version and play with it.

Note however, I observe a strange behavior of cars (in general) that I
found a little bit annoying (not specific to 1.3.5 version) :

When a car skids by rolling on the side track (grass), it begins to skid in
every direction and finally systematically turns backwards (in the
opposite direction
of the race).
The fact taht a car skids on the grass sounds rather normal to me, but why
is never occasionally ends up facing the track direction?

Is there an algorithm somewhere that always moves the car in reverse when
the car is doing a few slew round ?

best regards
(I'm posting this comment / question, but I appreciate this software: I play it
regularly)

-- 
*Arnaud Ceyrolle*

Hi Michael

Another thing, I guess this was you:
http://www.youtube.com/all_comments?v=b49l7FGc3TU

Because Google screwed somehow the comment system up, I was not able to 
answer there, it tells me that I do not have permission (in my channel, 
ouch...).

So I answer here:
- If you have downloaded the Windows installer the .ac files are not 
included, but you can have a look here how to get it:
http://youtu.be/ZhiW3mfmiBk?t=33s

Kind regards

Bernhard


On 11/20/2013 06:51 AM, Michael Symons wrote:
> Hello,
>
> I am a TORCS user who uses TORCS for driving only. I have recently had
> some problems as all of the cars are experiencing significant amounts of
> wheel spin in 1st gear. The problem I most profound in car1-ow1 where it
> is nearly impossible to start, and even more difficult to control on
> exit in 1st gear corners. When accelerating, the car has next to no
> traction and occasionally just spins in circles. A way of fixing this
> problem would be much appreciated.
>
> Yours Sincerely, Michael (CaptMike22)
>
> This message is intended for the addressee named and may contain
> privileged information
> or confidential information or both. If you are not the intended recipient
> please delete it and notify the sender.
>
>
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Torcs-users mailing list
> Tor...@li...
> https://lists.sourceforge.net/lists/listinfo/torcs-users
>

Hi Michael

Sounds like it is working as intended, either switch on traction control 
(usually the "z" key, depends on your players configuration) or just 
apply partial power. If you drive with keyboard do not use "pro" mode, 
or if you cannot resist, accelerate by tapping the accelerator.

What is your input method btw? Here are some videos of me driving with 
visible input:
- http://youtu.be/UrrpRPuyR7k (10 laps with gamepad)
- http://youtu.be/OHU0PFt1w6M (gamepad setup)
- http://youtu.be/euGXPoPlyMA (steering wheel setup)

If you use the most recent version (1.3.5) you have additional 
opportunities:
- In the car setup screen make the first gear longer (-> less torque 
from the drivetrain on the wheel in the changed gear)
- Make the whole diff ratio longer (-> less torque in all gears)
- If the car has a limited slip differential reduce the "accel locking 
torque", e.g. a value of "500".

Hope this helps, please report back.

Kind regards

Bernhard

On 11/20/2013 06:51 AM, Michael Symons wrote:
> Hello,
>
> I am a TORCS user who uses TORCS for driving only. I have recently had
> some problems as all of the cars are experiencing significant amounts of
> wheel spin in 1st gear. The problem I most profound in car1-ow1 where it
> is nearly impossible to start, and even more difficult to control on
> exit in 1st gear corners. When accelerating, the car has next to no
> traction and occasionally just spins in circles. A way of fixing this
> problem would be much appreciated.
>
> Yours Sincerely, Michael (CaptMike22)
>
> This message is intended for the addressee named and may contain
> privileged information
> or confidential information or both. If you are not the intended recipient
> please delete it and notify the sender.
>
>
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Torcs-users mailing list
> Tor...@li...
> https://lists.sourceforge.net/lists/listinfo/torcs-users
>

Hello,

I am a TORCS user who uses TORCS for driving only. I have recently had some
problems as all of the cars are experiencing significant amounts of wheel
spin in 1st gear. The problem I most profound in car1-ow1 where it is
nearly impossible to start, and even more difficult to control on exit in
1st gear corners. When accelerating, the car has next to no traction and
occasionally just spins in circles. A way of fixing this problem would be
much appreciated.

Yours Sincerely, Michael (CaptMike22)


This message is intended for the addressee named and may contain privileged information
or confidential information or both. If you are not the intended recipient
please delete it and notify the sender.

Hi Evgenios

Looks perfect... so I have no idea what's wrong:-(

Anybody else?

Best regards

Bernhard

On 11/18/2013 06:31 PM, Evgenios Kastanias wrote:
> Bernhard Wymann <berniw <at> bluewin.ch> writes:
>
>>
>> Hi Evgenios
>>
>> Uff, looks all pretty good (I will have another look tomorrow), only the
>> "torcs -l" is weird, I run out of ideas...
>>
>> Can you publish as well the generated "torcs" script and the output of
>> "cd ~/torcs_bin; tree lib" (maybe you have to install "tree" first).
>>
>> Just to review if the generated torcs script makes sense and if the
>> files are there. What would be interesting as well is the location of
>> libopenal.so.* files for example. But somehow it does not even miss it.
>>
>> Best regards
>>
>> Bernhard
>
> Hi, sorry for not replying sooner. This the output of tree lib
>
> lib
> └── torcs
>      ├── accc-bin
>      ├── drivers
>      │   ├── berniw
>      │   │   └── berniw.so
>      │   ├── berniw2
>      │   │   └── berniw2.so
>      │   ├── berniw3
>      │   │   └── berniw3.so
>      │   ├── bt
>      │   │   └── bt.so
>      │   ├── damned
>      │   │   └── damned.so
>      │   ├── human
>      │   │   └── human.so
>      │   ├── inferno
>      │   │   └── inferno.so
>      │   ├── inferno2
>      │   │   └── inferno2.so
>      │   ├── lliaw
>      │   │   └── lliaw.so
>      │   ├── olethros
>      │   │   └── olethros.so
>      │   ├── sparkle
>      │   │   └── sparkle.so
>      │   └── tita
>      │       └── tita.so
>      ├── lib
>      │   ├── libclient.so
>      │   ├── libconfscreens.so
>      │   ├── liblearning.so
>      │   ├── libmusicplayer.so
>      │   ├── libraceengine.so
>      │   ├── libracescreens.so
>      │   ├── librobottools.so
>      │   ├── libtgfclient.so
>      │   ├── libtgf.so
>      │   └── libtxml.so
>      ├── modules
>      │   ├── graphic
>      │   │   └── ssggraph.so
>      │   ├── simu
>      │   │   └── simuv2.so
>      │   ├── telemetry
>      │   │   └── telemetry.so
>      │   └── track
>      │       └── track.so
>      ├── nfs2ac-bin
>      ├── nfsperf-bin
>      ├── setup_linux.sh
>      ├── texmapper-bin
>      ├── torcs-bin
>      └── trackgen-bin
>
>
> And I hope this is the correct torcs script:
>
> #! /bin/bash
> # src/linux/torcs.  Generated from torcs.in by configure.
>
> ############################################################################
> ##
> #
> #    file                 : torcs.in
> #    created              : Sat Sep 11 20:20:04 CEST 1999
> #    copyright            : (C) 1999 by Eric Espie
> #    email                : to...@fr...
> #    version              : $Id: torcs.in,v 1.5.2.4 2012/06/01 01:59:42
> berniw Exp $
> #
> ############################################################################
> ##
> #
> #   This program is free software; you can redistribute it and/or modify
> #   it under the terms of the GNU General Public License as published by
> #   the Free Software Foundation; either version 2 of the License, or
> #   (at your option) any later version.
> #
> ############################################################################
> ##
>
> prefix=/home/evgenios/torcs_bin
> exec_prefix=${prefix}
>
> BINDIR=${exec_prefix}/bin
> LIBDIR=${exec_prefix}/lib/torcs
> DATAROOTDIR=${prefix}/share
> DATADIR=$DATAROOTDIR/games/torcs
> VARDIR=${prefix}/var/games/torcs
>
> LOCAL_CONF=$HOME/.torcs
>
> if [ -d $DATADIR ]
> then
>      if [ ! -d $LOCAL_CONF ]
>      then
> 	rm -rf $LOCAL_CONF
> 	mkdir -p $LOCAL_CONF
> 	echo "$LOCAL_CONF created, copying/linking game data"
>      fi
>      export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}$LIBDIR/lib
>      cd $DATADIR
>      if [ -f $LIBDIR/setup_linux.sh ]
>      then
> 	/bin/bash $LIBDIR/setup_linux.sh $LOCAL_CONF
> 	if [ $? -ne 0 ]
> 	then
> 	    exit 1
> 	fi
>      else
> 	echo "$LIBDIR/setup_linux.sh file does not exist, check your
> installation"
> 	exit 1
>      fi
>      case $1 in
> 	# List the library used
> 	-l) shift
> 	    ldd $LIBDIR/torcs-bin
> 	    ;;
>
> 	# Run under GDB
> 	-d) shift
> 	    gdb  $LIBDIR/torcs-bin <<EOF
> r -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*
> bt
> EOF
> 	    ;;
>
> 	-g) shift
> 	    valgrind --leak-check=yes --log-file=$LOCAL_CONF/valgrind.log
> $LIBDIR/torcs-bin -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*
> 	    ;;
>
> 	-e) shift
> 	    echo "cd $DATADIR"
> 	    echo "export LD_LIBRARY_PATH=$LIBDIR/lib:$LD_LIBRARY_PATH"
> 	    echo "gdb  $LIBDIR/torcs-bin"
> 	    echo "r -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*"
> 	    ;;
>
> 	-h)
> 	    echo "usage: torcs [-l|-d|-g|-e] [-s] [-r]"
> 	    echo "   -l  list the dynamically linked libraries"
> 	    echo "   -d  run under gdb and print stack trace on exit"
> 		echo "   -g  run under valgrind (requires a debug build for
> useful results)"
> 	    echo "   -e  display the commands to issue when you want to run
> under gdb"
> 		echo "   -s  disable multitexturing, important for older
> graphics cards"
> 		echo "   -r  run race in command line mode, see FAQ for
> details"
> 		echo "   -k  suppress dlclose for modules (useful to get
> symbol information with valgrind)"
> 	    ;;
>
> 	# Normal run
> 	*) $LIBDIR/torcs-bin -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*
> 	    ;;
>
>      esac
>      exit 0
> fi
>
> echo "TORCS location not found"
> 	
> 	
>
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
> _______________________________________________
> Torcs-users mailing list
> Tor...@li...
> https://lists.sourceforge.net/lists/listinfo/torcs-users
>

Bernhard Wymann <berniw <at> bluewin.ch> writes:

> 
> Hi Evgenios
> 
> Uff, looks all pretty good (I will have another look tomorrow), only the 
> "torcs -l" is weird, I run out of ideas...
> 
> Can you publish as well the generated "torcs" script and the output of 
> "cd ~/torcs_bin; tree lib" (maybe you have to install "tree" first).
> 
> Just to review if the generated torcs script makes sense and if the 
> files are there. What would be interesting as well is the location of 
> libopenal.so.* files for example. But somehow it does not even miss it.
> 
> Best regards
> 
> Bernhard

Hi, sorry for not replying sooner. This the output of tree lib

lib
└── torcs
    ├── accc-bin
    ├── drivers
    │   ├── berniw
    │   │   └── berniw.so
    │   ├── berniw2
    │   │   └── berniw2.so
    │   ├── berniw3
    │   │   └── berniw3.so
    │   ├── bt
    │   │   └── bt.so
    │   ├── damned
    │   │   └── damned.so
    │   ├── human
    │   │   └── human.so
    │   ├── inferno
    │   │   └── inferno.so
    │   ├── inferno2
    │   │   └── inferno2.so
    │   ├── lliaw
    │   │   └── lliaw.so
    │   ├── olethros
    │   │   └── olethros.so
    │   ├── sparkle
    │   │   └── sparkle.so
    │   └── tita
    │       └── tita.so
    ├── lib
    │   ├── libclient.so
    │   ├── libconfscreens.so
    │   ├── liblearning.so
    │   ├── libmusicplayer.so
    │   ├── libraceengine.so
    │   ├── libracescreens.so
    │   ├── librobottools.so
    │   ├── libtgfclient.so
    │   ├── libtgf.so
    │   └── libtxml.so
    ├── modules
    │   ├── graphic
    │   │   └── ssggraph.so
    │   ├── simu
    │   │   └── simuv2.so
    │   ├── telemetry
    │   │   └── telemetry.so
    │   └── track
    │       └── track.so
    ├── nfs2ac-bin
    ├── nfsperf-bin
    ├── setup_linux.sh
    ├── texmapper-bin
    ├── torcs-bin
    └── trackgen-bin


And I hope this is the correct torcs script:

#! /bin/bash
# src/linux/torcs.  Generated from torcs.in by configure.

############################################################################
##
#
#    file                 : torcs.in
#    created              : Sat Sep 11 20:20:04 CEST 1999
#    copyright            : (C) 1999 by Eric Espie                         
#    email                : to...@fr...   
#    version              : $Id: torcs.in,v 1.5.2.4 2012/06/01 01:59:42 
berniw Exp $                                  
#
############################################################################
##
#
#   This program is free software; you can redistribute it and/or modify
#   it under the terms of the GNU General Public License as published by
#   the Free Software Foundation; either version 2 of the License, or
#   (at your option) any later version.
#
############################################################################
##

prefix=/home/evgenios/torcs_bin
exec_prefix=${prefix}

BINDIR=${exec_prefix}/bin
LIBDIR=${exec_prefix}/lib/torcs
DATAROOTDIR=${prefix}/share
DATADIR=$DATAROOTDIR/games/torcs
VARDIR=${prefix}/var/games/torcs

LOCAL_CONF=$HOME/.torcs

if [ -d $DATADIR ]
then
    if [ ! -d $LOCAL_CONF ]
    then
	rm -rf $LOCAL_CONF
	mkdir -p $LOCAL_CONF
	echo "$LOCAL_CONF created, copying/linking game data"
    fi
    export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}$LIBDIR/lib
    cd $DATADIR
    if [ -f $LIBDIR/setup_linux.sh ]
    then
	/bin/bash $LIBDIR/setup_linux.sh $LOCAL_CONF
	if [ $? -ne 0 ]
	then
	    exit 1
	fi
    else
	echo "$LIBDIR/setup_linux.sh file does not exist, check your 
installation"
	exit 1
    fi
    case $1 in
	# List the library used
	-l) shift
	    ldd $LIBDIR/torcs-bin
	    ;;

	# Run under GDB
	-d) shift
	    gdb  $LIBDIR/torcs-bin <<EOF
r -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*
bt
EOF
	    ;;

	-g) shift
	    valgrind --leak-check=yes --log-file=$LOCAL_CONF/valgrind.log 
$LIBDIR/torcs-bin -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*
	    ;;

	-e) shift
	    echo "cd $DATADIR"
	    echo "export LD_LIBRARY_PATH=$LIBDIR/lib:$LD_LIBRARY_PATH"
	    echo "gdb  $LIBDIR/torcs-bin"
	    echo "r -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*"
	    ;;

	-h)
	    echo "usage: torcs [-l|-d|-g|-e] [-s] [-r]"
	    echo "   -l  list the dynamically linked libraries"
	    echo "   -d  run under gdb and print stack trace on exit"
		echo "   -g  run under valgrind (requires a debug build for 
useful results)"
	    echo "   -e  display the commands to issue when you want to run 
under gdb"
		echo "   -s  disable multitexturing, important for older 
graphics cards"
		echo "   -r  run race in command line mode, see FAQ for 
details"
		echo "   -k  suppress dlclose for modules (useful to get 
symbol information with valgrind)"
	    ;;

	# Normal run
	*) $LIBDIR/torcs-bin -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*
	    ;;

    esac
    exit 0
fi

echo "TORCS location not found"
	
	

Hi Torcs-mailing-list.

We are two people working on a university project where we use the Torcs
framework. We write our client in Java using the Championship2010 UDP
connection and the Text-Only mode of the Torcs server.
When performing tests with our controller we have noticed that the
simulation itself doesn't take much time (about 0,1 second) but restarting
the server (by the meta-action) takes a very long time, 10,1 seconds when
we measured it last. This is a huge difference, and something we would like
to reduce. Have anyone else experienced this, located the problem and found
any solution to it?

Thanks in advance
Emil Juul Jacobsen & Jacob Dinesen

Hi all

TORCS version 1.3.5 is available, visit www.torcs.org for details.

Enjoy, Bernhard.

Hi Evgenios

Uff, looks all pretty good (I will have another look tomorrow), only the 
"torcs -l" is weird, I run out of ideas...

Can you publish as well the generated "torcs" script and the output of 
"cd ~/torcs_bin; tree lib" (maybe you have to install "tree" first).

Just to review if the generated torcs script makes sense and if the 
files are there. What would be interesting as well is the location of 
libopenal.so.* files for example. But somehow it does not even miss it.

Best regards

Bernhard

On 11/15/2013 12:07 AM, Evgenios Kastanias wrote:
>
>> Another question, is the Ubuntu machine yours, or is it an old tortured
>> machine where many students had root access without replacing the image?
>
> No, its my machine with Ubuntu 13.04 on it.
>
>
>> What is the output of "find . -type f -exec objdump -f {} \; | grep
>> architecture" in the lib directory (directory here is ~/torcs_bin/lib64)?
>
> I couldn't find any directory like /torcs_bin/lib64 so I ran the command in
> torcs-bin/lib and this is the output
>
> architecture: i386:x86-64, flags 0x00000112:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000112:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000112:
> objdump: ./torcs/setup_linux.sh: File format not recognised
> architecture: i386:x86-64, flags 0x00000112:
> architecture: i386:x86-64, flags 0x00000112:
> architecture: i386:x86-64, flags 0x00000112:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
> architecture: i386:x86-64, flags 0x00000150:
>
>
>> Just to go sure, could you post config.log and the compiler output (make
>> clean, make >& build.log, and a full dump of ~/torcs_bin/bin/torcs -l >&
>> ldd.log).
>
>
> The config.log is here
>
> http://pastebin.com/YPfAyVGR
>
> The build.log is here
>
> http://pastebin.com/MekQTFT8
>
> and the dump of  ~/torcs_bin/bin/torcs -l >& ldd.log is this
>
> 	linux-vdso.so.1 =>  (0x00007fff6a315000)
> 	libclient.so => /home/evgenios/torcs_bin/lib/torcs/lib/libclient.so
> (0x00007f1a939c1000)
> 	libtgf.so => /home/evgenios/torcs_bin/lib/torcs/lib/libtgf.so
> (0x00007f1a939b5000)
> 	libtgfclient.so =>
> /home/evgenios/torcs_bin/lib/torcs/lib/libtgfclient.so (0x00007f1a93998000)
> 	libraceengine.so =>
> /home/evgenios/torcs_bin/lib/torcs/lib/libraceengine.so (0x00007f1a93987000)
> 	libglut.so.3 => /usr/lib/x86_64-linux-gnu/libglut.so.3
> (0x00007f1a93741000)
> 	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f1a93524000)
> 	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1a9315b000)
> 	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x00007f1a92e58000)
> 	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1a92b52000)
> 	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> (0x00007f1a9293c000)
> 	libracescreens.so =>
> /home/evgenios/torcs_bin/lib/torcs/lib/libracescreens.so
> (0x00007f1a9292a000)
> 	librobottools.so =>
> /home/evgenios/torcs_bin/lib/torcs/lib/librobottools.so (0x00007f1a92921000)
> 	libGL.so.1 => /usr/lib/nvidia-310/libGL.so.1 (0x00007f1a925fe000)
> 	libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
> (0x00007f1a922c4000)
> 	/lib64/ld-linux-x86-64.so.2 (0x00007f1a93e7b000)
> 	libnvidia-tls.so.310.44 => /usr/lib/nvidia-310/tls/libnvidia-
> tls.so.310.44 (0x00007f1a920c0000)
> 	libnvidia-glcore.so.310.44 => /usr/lib/nvidia-310/libnvidia-
> glcore.so.310.44 (0x00007f1a8fbcd000)
> 	libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
> (0x00007f1a8f9ba000)
> 	libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
> (0x00007f1a8f79c000)
> 	libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
> (0x00007f1a8f598000)
> 	libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
> (0x00007f1a8f391000)
>
> I took the liberty of using pastebin for the other 2 logs, since they were
> massive and it would take alof of space here. I notice some errors too in
> the config log but I don't know what to make out of them.
>
> Thanks again for helping me out!
>
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> Torcs-users mailing list
> Tor...@li...
> https://lists.sourceforge.net/lists/listinfo/torcs-users
>

Hi,

I grep'd Torcs sources for XML_ParserCreate of a successful build
and got the following:


$ find . -print0 | xargs -0 grep XML_ParserCreate
./libs/txml/xml.cpp:    parser = XML_ParserCreate((XML_Char*)NULL);
Binary file ./libs/txml/xml.o matches
Binary file ./libs/txml/libtxml.so matches
./libs/txml/txml.def:   XML_ParserCreate
Binary file ./libs/txml/xmlparse.o matches
./libs/txml/xmlparse.h:XML_ParserCreate(const XML_Char *encoding);
./libs/txml/xmlparse.c:XML_Parser XML_ParserCreate(const XML_Char *encodingName)
./libs/txml/xmlparse.c:  parser = XML_ParserCreate(encodingName);
./libs/tgf/params.cpp:    parmHandle->parser = XML_ParserCreate((XML_Char*)NULL);
Binary file ./libs/tgf/params.o matches
Binary file ./libs/tgf/libtgf.so matches

To try this yourself, type the following after you have compiled TORCS:

cd ~/torcs-1.3.5-test1/src
find . -print0 | xargs -0 grep XML_ParserCreate

Maybe this will provide some hints.

David Savinkoff

> Another question, is the Ubuntu machine yours, or is it an old tortured 
> machine where many students had root access without replacing the image?

No, its my machine with Ubuntu 13.04 on it. 


> What is the output of "find . -type f -exec objdump -f {} \; | grep 
> architecture" in the lib directory (directory here is ~/torcs_bin/lib64)?

I couldn't find any directory like /torcs_bin/lib64 so I ran the command in 
torcs-bin/lib and this is the output

architecture: i386:x86-64, flags 0x00000112:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000112:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000112:
objdump: ./torcs/setup_linux.sh: File format not recognised
architecture: i386:x86-64, flags 0x00000112:
architecture: i386:x86-64, flags 0x00000112:
architecture: i386:x86-64, flags 0x00000112:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:
architecture: i386:x86-64, flags 0x00000150:


> Just to go sure, could you post config.log and the compiler output (make 
> clean, make >& build.log, and a full dump of ~/torcs_bin/bin/torcs -l >& 
> ldd.log).


The config.log is here 

http://pastebin.com/YPfAyVGR

The build.log is here

http://pastebin.com/MekQTFT8

and the dump of  ~/torcs_bin/bin/torcs -l >& ldd.log is this

	linux-vdso.so.1 =>  (0x00007fff6a315000)
	libclient.so => /home/evgenios/torcs_bin/lib/torcs/lib/libclient.so 
(0x00007f1a939c1000)
	libtgf.so => /home/evgenios/torcs_bin/lib/torcs/lib/libtgf.so 
(0x00007f1a939b5000)
	libtgfclient.so => 
/home/evgenios/torcs_bin/lib/torcs/lib/libtgfclient.so (0x00007f1a93998000)
	libraceengine.so => 
/home/evgenios/torcs_bin/lib/torcs/lib/libraceengine.so (0x00007f1a93987000)
	libglut.so.3 => /usr/lib/x86_64-linux-gnu/libglut.so.3 
(0x00007f1a93741000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f1a93524000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1a9315b000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x00007f1a92e58000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1a92b52000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x00007f1a9293c000)
	libracescreens.so => 
/home/evgenios/torcs_bin/lib/torcs/lib/libracescreens.so 
(0x00007f1a9292a000)
	librobottools.so => 
/home/evgenios/torcs_bin/lib/torcs/lib/librobottools.so (0x00007f1a92921000)
	libGL.so.1 => /usr/lib/nvidia-310/libGL.so.1 (0x00007f1a925fe000)
	libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x00007f1a922c4000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f1a93e7b000)
	libnvidia-tls.so.310.44 => /usr/lib/nvidia-310/tls/libnvidia-
tls.so.310.44 (0x00007f1a920c0000)
	libnvidia-glcore.so.310.44 => /usr/lib/nvidia-310/libnvidia-
glcore.so.310.44 (0x00007f1a8fbcd000)
	libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 
(0x00007f1a8f9ba000)
	libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 
(0x00007f1a8f79c000)
	libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 
(0x00007f1a8f598000)
	libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 
(0x00007f1a8f391000)

I took the liberty of using pastebin for the other 2 logs, since they were 
massive and it would take alof of space here. I notice some errors too in 
the config log but I don't know what to make out of them.

Thanks again for helping me out! 

Hi Evgenios

If you tried with 1.3.4 or earlier you could try this:
make distclean
export CFLAGS=""-Wl,--no-as-needed"
export CPPFLAGS="-Wl,--no-as-needed"
export CXXFLAGS="-Wl,--no-as-needed"
./configure --prefix=$HOME/torcs_bin
make
make install
make datainstall

Best regards

Bernhard

On 11/14/2013 10:38 PM, Evgenios Kastanias wrote:
>
>> It doesn't, it points hopefully to the libraries in $HOME/torcs_bin/...,
>> does it?
>>
>
> Yeah I meant that no new libraries are here, they are just in the
> $HOME/torcs_bin/ as you said.
>
> linux-vdso.so.1 =>  (0x00007fff78ffe000)
> 	libclient.so => /home/evgenios/torcs_bin/lib/torcs/lib/libclient.so
> (0x00007f170e48d000)
> 	libtgf.so => /home/evgenios/torcs_bin/lib/torcs/lib/libtgf.so
> (0x00007f170e481000)
> 	libtgfclient.so =>
> /home/evgenios/torcs_bin/lib/torcs/lib/libtgfclient.so (0x00007f170e464000)
> 	libraceengine.so =>
> /home/evgenios/torcs_bin/lib/torcs/lib/libraceengine.so (0x00007f170e453000)
> 	libglut.so.3 => /usr/lib/x86_64-linux-gnu/libglut.so.3
> (0x00007f170e20d000)
> 	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f170dff0000)
> 	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f170dc27000)
> 	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x00007f170d924000)
> 	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f170d61e000)
> 	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> (0x00007f170d408000)
> 	libracescreens.so =>
> /home/evgenios/torcs_bin/lib/torcs/lib/libracescreens.so
> (0x00007f170d3f6000)
> 	librobottools.so =>
> /home/evgenios/torcs_bin/lib/torcs/lib/librobottools.so (0x00007f170d3ed000)
> 	libGL.so.1 => /usr/lib/nvidia-310/libGL.so.1 (0x00007f170d0ca000)
> 	libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
> (0x00007f170cd90000)
> 	/lib64/ld-linux-x86-64.so.2 (0x00007f170e947000)
> 	libnvidia-tls.so.310.44 => /usr/lib/nvidia-310/tls/libnvidia-
> tls.so.310.44 (0x00007f170cb8c000)
> 	libnvidia-glcore.so.310.44 => /usr/lib/nvidia-310/libnvidia-
> glcore.so.310.44 (0x00007f170a699000)
> 	libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
> (0x00007f170a486000)
> 	libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
> (0x00007f170a268000)
> 	libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
> (0x00007f170a064000)
> 	libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
> (0x00007f1709e5d000)
>
>
> Also this the error I get now, still the same but different directories
> since torcs is install in $HOME/torcs_bin/
>
> /home/evgenios/torcs_bin/lib/torcs/torcs-bin: symbol lookup error:
> /home/evgenios/torcs_bin/lib/torcs/lib/libtgf.so: undefined symbol:
> XML_ParserCreate
>
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> Torcs-users mailing list
> Tor...@li...
> https://lists.sourceforge.net/lists/listinfo/torcs-users
>

Hi Evgenios

Another question, is the Ubuntu machine yours, or is it an old tortured 
machine where many students had root access without replacing the image?

Just Googling a bit around: "undefined symbol: XML_ParserCreate":
http://www.unidata.ucar.edu/support/help/MailArchives/udunits/msg00802.html
-> problem with $LDFLAGS

What is the output of "find . -type f -exec objdump -f {} \; | grep 
architecture" in the lib directory (directory here is ~/torcs_bin/lib64)?

Just to go sure, could you post config.log and the compiler output (make 
clean, make >& build.log, and a full dump of ~/torcs_bin/bin/torcs -l >& 
ldd.log).

Best regards

Bernhard

On 11/14/2013 10:08 PM, Evgenios Kastanias wrote:
> Bernhard Wymann <berniw <at> bluewin.ch> writes:
>
>>
>
>> I suggest performing this experiment: build TORCS from fresh extracted
>> sources into your home directory and run it from there (this way you
>> have not to fight with permissions/root):
>> 1. Make sure that your environment variables are empty, check "echo
>> $MAKE_DEFAULT" and "echo $TORCS_BASE" (you can set them later again for
>> robot development if required)
>> 2. Make sure that "echo $CFLAGS", "echo $CPPFLAGS" and "echo $CXXFLAGS"
>> are empty or do not contain weird stuff
>> 3. configure with "./configure --prefix=$HOME/torcs_bin"
>> 4. "make", "make install", "make datainstall"
>> 5. start TORCS with "~/torcs_bin/bin/torcs" (or wherever it has been
>> placed).
>>
>
> Ok, I ran ldconfig, still the same. Then I followed your instructions,
> redownloaded torcs, made sure the environmental variables where empty and did
> the install in home. Still the same. Doing ~/torcs_bin/bin/torcs -l produces
> the same libraries as before.
>
> Thanks for the help!
>
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> Torcs-users mailing list
> Tor...@li...
> https://lists.sourceforge.net/lists/listinfo/torcs-users
>

> It doesn't, it points hopefully to the libraries in $HOME/torcs_bin/..., 
> does it?
> 

Yeah I meant that no new libraries are here, they are just in the 
$HOME/torcs_bin/ as you said.

linux-vdso.so.1 =>  (0x00007fff78ffe000)
	libclient.so => /home/evgenios/torcs_bin/lib/torcs/lib/libclient.so 
(0x00007f170e48d000)
	libtgf.so => /home/evgenios/torcs_bin/lib/torcs/lib/libtgf.so 
(0x00007f170e481000)
	libtgfclient.so => 
/home/evgenios/torcs_bin/lib/torcs/lib/libtgfclient.so (0x00007f170e464000)
	libraceengine.so => 
/home/evgenios/torcs_bin/lib/torcs/lib/libraceengine.so (0x00007f170e453000)
	libglut.so.3 => /usr/lib/x86_64-linux-gnu/libglut.so.3 
(0x00007f170e20d000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f170dff0000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f170dc27000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x00007f170d924000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f170d61e000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x00007f170d408000)
	libracescreens.so => 
/home/evgenios/torcs_bin/lib/torcs/lib/libracescreens.so 
(0x00007f170d3f6000)
	librobottools.so => 
/home/evgenios/torcs_bin/lib/torcs/lib/librobottools.so (0x00007f170d3ed000)
	libGL.so.1 => /usr/lib/nvidia-310/libGL.so.1 (0x00007f170d0ca000)
	libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x00007f170cd90000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f170e947000)
	libnvidia-tls.so.310.44 => /usr/lib/nvidia-310/tls/libnvidia-
tls.so.310.44 (0x00007f170cb8c000)
	libnvidia-glcore.so.310.44 => /usr/lib/nvidia-310/libnvidia-
glcore.so.310.44 (0x00007f170a699000)
	libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 
(0x00007f170a486000)
	libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 
(0x00007f170a268000)
	libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 
(0x00007f170a064000)
	libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 
(0x00007f1709e5d000)


Also this the error I get now, still the same but different directories 
since torcs is install in $HOME/torcs_bin/

/home/evgenios/torcs_bin/lib/torcs/torcs-bin: symbol lookup error: 
/home/evgenios/torcs_bin/lib/torcs/lib/libtgf.so: undefined symbol: 
XML_ParserCreate

And now you have rebuilt it from source,
what is the error when you run Torcs ?

regards


2013/11/14 Bernhard Wymann <be...@bl...>

> Hi Evgenios
>
> So it does still not work, hmm...
>
> > Ok, I ran ldconfig, still the same. Then I followed your instructions,
> > redownloaded torcs, made sure the environmental variables where empty
> and did
> > the install in home. Still the same. Doing ~/torcs_bin/bin/torcs -l
> produces
> > the same libraries as before.
>
> It doesn't, it points hopefully to the libraries in $HOME/torcs_bin/...,
> does it?
>
> Best regards
>
> Bernhard
>
>
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> Torcs-users mailing list
> Tor...@li...
> https://lists.sourceforge.net/lists/listinfo/torcs-users
>



-- 
*Arnaud Ceyrolle*

Hi Evgenios

So it does still not work, hmm...

> Ok, I ran ldconfig, still the same. Then I followed your instructions,
> redownloaded torcs, made sure the environmental variables where empty and did
> the install in home. Still the same. Doing ~/torcs_bin/bin/torcs -l produces
> the same libraries as before.

It doesn't, it points hopefully to the libraries in $HOME/torcs_bin/..., 
does it?

Best regards

Bernhard

Bernhard Wymann <berniw <at> bluewin.ch> writes:

> 

> I suggest performing this experiment: build TORCS from fresh extracted 
> sources into your home directory and run it from there (this way you 
> have not to fight with permissions/root):
> 1. Make sure that your environment variables are empty, check "echo 
> $MAKE_DEFAULT" and "echo $TORCS_BASE" (you can set them later again for 
> robot development if required)
> 2. Make sure that "echo $CFLAGS", "echo $CPPFLAGS" and "echo $CXXFLAGS" 
> are empty or do not contain weird stuff
> 3. configure with "./configure --prefix=$HOME/torcs_bin"
> 4. "make", "make install", "make datainstall"
> 5. start TORCS with "~/torcs_bin/bin/torcs" (or wherever it has been 
> placed).
> 

Ok, I ran ldconfig, still the same. Then I followed your instructions, 
redownloaded torcs, made sure the environmental variables where empty and did 
the install in home. Still the same. Doing ~/torcs_bin/bin/torcs -l produces 
the same libraries as before. 

Thanks for the help!

Hi Evgenios

Is this all output of torcs -l, there is missing a lot of stuff (vorbis, 
openal, parts of torcs, ...)?

Can you try to run as root "ldconfig", and then try again, and if that 
not helps restart the system? Does this help?

What is suspect is that some libs are in /usr/local/lib... and some in 
/usr/lib/x86_64..., this raises the question if this is normal on this 
system or if you have mixed up somehow 64 and 32 bit stuff, e.g my torcs 
-l output is like this and pretty consistent:

         linux-vdso.so.1 (0x00007fff1cdff000)
         libopenal.so.1 => /usr/lib64/libopenal.so.1 (0x00007f59339b2000)
         libalut.so.0 => /usr/lib64/libalut.so.0 (0x00007f59337aa000)
         libvorbisfile.so.3 => /usr/lib64/libvorbisfile.so.3 
(0x00007f59335a1000)
         libracescreens.so => 
/home/berni/torcs_bin/lib64/torcs/lib/libracescreens.so (0x00007f5933390000)
         librobottools.so => 
/home/berni/torcs_bin/lib64/torcs/lib/librobottools.so (0x00007f5933189000)
         libclient.so => 
/home/berni/torcs_bin/lib64/torcs/lib/libclient.so (0x00007f5932ad3000)
         libconfscreens.so => 
/home/berni/torcs_bin/lib64/torcs/lib/libconfscreens.so (0x00007f59328c5000)
         libtgf.so => /home/berni/torcs_bin/lib64/torcs/lib/libtgf.so 
(0x00007f59326b9000)
         libtgfclient.so => 
/home/berni/torcs_bin/lib64/torcs/lib/libtgfclient.so (0x00007f593249e000)
         libtxml.so => /home/berni/torcs_bin/lib64/torcs/lib/libtxml.so 
(0x00007f593227f000)
         libraceengine.so => 
/home/berni/torcs_bin/lib64/torcs/lib/libraceengine.so (0x00007f593206f000)
         libmusicplayer.so => 
/home/berni/torcs_bin/lib64/torcs/lib/libmusicplayer.so (0x00007f5931e69000)
         liblearning.so => 
/home/berni/torcs_bin/lib64/torcs/lib/liblearning.so (0x00007f5931c54000)
         libglut.so.3 => /usr/lib64/libglut.so.3 (0x00007f5931a09000)
         libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x00007f593178a000)
         libGL.so.1 => /usr/X11R6/lib64/libGL.so.1 (0x00007f593145c000)
         libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x00007f5931232000)
         libz.so.1 => /lib64/libz.so.1 (0x00007f593101c000)
         libdl.so.2 => /lib64/libdl.so.2 (0x00007f5930e18000)
         libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007f5930c0e000)
         libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f5930a04000)
         libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x00007f59307fe000)
         libXmu.so.6 => /usr/lib64/libXmu.so.6 (0x00007f59305e3000)
         libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007f59303d3000)
         libXt.so.6 => /usr/lib64/libXt.so.6 (0x00007f593016c000)
         libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f592ff64000)
         libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f592fd48000)
         libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f592fb36000)
         libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f592f7fa000)
         libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f592f4f4000)
         libm.so.6 => /lib64/libm.so.6 (0x00007f592f1f6000)
         libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f592efdf000)
         libc.so.6 => /lib64/libc.so.6 (0x00007f592ec31000)
         librt.so.1 => /lib64/librt.so.1 (0x00007f592ea29000)
         libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f592e80d000)
         libvorbis.so.0 => /usr/lib64/libvorbis.so.0 (0x00007f592e5df000)
         libogg.so.0 => /usr/lib64/libogg.so.0 (0x00007f592e3d8000)
         libnvidia-tls.so.319.32 => 
/usr/lib64/tls/libnvidia-tls.so.319.32 (0x00007f592e1d5000)
         libnvidia-glcore.so.319.32 => 
/usr/lib64/libnvidia-glcore.so.319.32 (0x00007f592bc7e000)
         /lib64/ld-linux-x86-64.so.2 (0x00007f5933c0a000)
         libuuid.so.1 => /usr/lib64/libuuid.so.1 (0x00007f592ba79000)
         libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f592b859000)
         libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f592b655000)


I suggest performing this experiment: build TORCS from fresh extracted 
sources into your home directory and run it from there (this way you 
have not to fight with permissions/root):
1. Make sure that your environment variables are empty, check "echo 
$MAKE_DEFAULT" and "echo $TORCS_BASE" (you can set them later again for 
robot development if required)
2. Make sure that "echo $CFLAGS", "echo $CPPFLAGS" and "echo $CXXFLAGS" 
are empty or do not contain weird stuff
3. configure with "./configure --prefix=$HOME/torcs_bin"
4. "make", "make install", "make datainstall"
5. start TORCS with "~/torcs_bin/bin/torcs" (or wherever it has been 
placed).

Best regards

Bernhard


On 11/14/2013 07:56 PM, Evgenios Kastanias wrote:
>
>> Can you post the output of "torcs -l"?
> linux-vdso.so.1 =>  (0x00007fff981fe000)
> 	libclient.so => /usr/local/lib/torcs/lib/libclient.so
> (0x00007f5f67baf000)
> 	libtgf.so => /usr/local/lib/torcs/lib/libtgf.so (0x00007f5f67ba3000)
> 	libtgfclient.so => /usr/local/lib/torcs/lib/libtgfclient.so
> (0x00007f5f67b86000)
> 	libraceengine.so => /usr/local/lib/torcs/lib/libraceengine.so
> (0x00007f5f67b75000)
> 	libglut.so.3 => /usr/lib/x86_64-linux-gnu/libglut.so.3
> (0x00007f5f67917000)
> 	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f5f67712000)
> 	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5f67349000)
> 	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x00007f5f67046000)
> 	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f5f66d40000)
> 	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> (0x00007f5f66b2a000)
> 	libracescreens.so => /usr/local/lib/torcs/lib/libracescreens.so
> (0x00007f5f66b18000)
> 	librobottools.so => /usr/local/lib/torcs/lib/librobottools.so
> (0x00007f5f66b0f000)
> 	libGL.so.1 => /usr/lib/nvidia-310/libGL.so.1 (0x00007f5f667ec000)
> 	libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
> (0x00007f5f664b2000)
> 	/lib64/ld-linux-x86-64.so.2 (0x00007f5f68069000)
> 	libnvidia-tls.so.310.44 => /usr/lib/nvidia-310/tls/libnvidia-
> tls.so.310.44 (0x00007f5f662ae000)
> 	libnvidia-glcore.so.310.44 => /usr/lib/nvidia-310/libnvidia-
> glcore.so.310.44 (0x00007f5f63dbb000)
> 	libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
> (0x00007f5f63ba9000)
> 	libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
> (0x00007f5f6398a000)
> 	libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
> (0x00007f5f63786000)
> 	libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
> (0x00007f5f6357f000)
>
>
>> No, not required, the only thing which needs some tweaking regarding 64
>> bit is plib (not part of TORCS itself), it must usually be compiled with
>> -fPIC
>
> Yes I compiled plib with -fPIC so I don't think its the issue either.
>
>
>> You need first to change to the directory containing libtgf.so, see
>> output of "torcs -l" to locate it (or use find/file browser).
>
> Ok, now the output is as you said
> nm libtgf.so | grep XML_ParserCreate
>                   U XML_ParserCreate
>
>
>> Btw. some other thought, if you are new to Linux, why are you using it
>> at all, what about using Windows for your work, would that be an option
>> (of course I encourage the use of Linux, but in the context of limited
>> time/fixed schedule it could make sense to use a familiar platform to
>> have less battles to fight...)?
>
> Yeah, I agree that with Windows I would have had less trouble but I was told
> by my supervisor to do this in Linux. To be honest I have learned alot
> despite all the issues I have!
>
> Also a poster below suggested that I run "ldd torcs-bin". It couldn't find
> some libraries like libtgf.so and libtgfclient.so all of them in the
> /usr/local/lib/torcs/lib directory so I added them to LD_LIBRARY_PATH.
> Unfortunately I still get the same error.
>
> Again I thank you for your time and effort in helping me!
>
>
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> Torcs-users mailing list
> Tor...@li...
> https://lists.sourceforge.net/lists/listinfo/torcs-users
>

Arnaud Ceyrolle <aceyrolle <at> googlemail.com> writes:


> Or you can list the libraries you are missing by doing a "ldd torcs-bin" 
on the binary of Torcs (not the shell) and then adding all the paths of the 
libraries it lists on the output to the LD_LIBRARY_PATH (only the Torcs-
specifics one).
> 
> Regards
> --
> Arnaud Ceyrolle

I follow your advice and sure enough when doing "ldd torcs-bin" it couldn't 
find the libraries in /usr/local/lib/torcs/lib like libtgf.so and so on.
I added the path to LD_LIBRARY_PATH and running the same command I get this 
output that it can find all of them

linux-vdso.so.1 =>  (0x00007fff08ffe000)
	libclient.so => /usr/local/lib/torcs/lib/libclient.so 
(0x00007f5c97034000)
	libtgf.so => /usr/local/lib/torcs/lib/libtgf.so (0x00007f5c97028000)
	libtgfclient.so => /usr/local/lib/torcs/lib/libtgfclient.so 
(0x00007f5c9700b000)
	libraceengine.so => /usr/local/lib/torcs/lib/libraceengine.so 
(0x00007f5c96ffa000)
	libglut.so.3 => /usr/lib/x86_64-linux-gnu/libglut.so.3 
(0x00007f5c96d9c000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f5c96b97000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5c967ce000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x00007f5c964cb000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f5c961c5000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x00007f5c95faf000)
	libracescreens.so => /usr/local/lib/torcs/lib/libracescreens.so 
(0x00007f5c95f9d000)
	librobottools.so => /usr/local/lib/torcs/lib/librobottools.so 
(0x00007f5c95f94000)
	libGL.so.1 => /usr/lib/nvidia-310/libGL.so.1 (0x00007f5c95c71000)
	libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x00007f5c95937000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f5c974ee000)
	libnvidia-tls.so.310.44 => /usr/lib/nvidia-310/tls/libnvidia-
tls.so.310.44 (0x00007f5c95733000)
	libnvidia-glcore.so.310.44 => /usr/lib/nvidia-310/libnvidia-
glcore.so.310.44 (0x00007f5c93240000)
	libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 
(0x00007f5c9302e000)
	libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 
(0x00007f5c92e0f000)
	libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 
(0x00007f5c92c0b000)
	libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 
(0x00007f5c92a04000)


But I get the same error again. Thanks for your help in my issue!

> Can you post the output of "torcs -l"?
linux-vdso.so.1 =>  (0x00007fff981fe000)
	libclient.so => /usr/local/lib/torcs/lib/libclient.so 
(0x00007f5f67baf000)
	libtgf.so => /usr/local/lib/torcs/lib/libtgf.so (0x00007f5f67ba3000)
	libtgfclient.so => /usr/local/lib/torcs/lib/libtgfclient.so 
(0x00007f5f67b86000)
	libraceengine.so => /usr/local/lib/torcs/lib/libraceengine.so 
(0x00007f5f67b75000)
	libglut.so.3 => /usr/lib/x86_64-linux-gnu/libglut.so.3 
(0x00007f5f67917000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f5f67712000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5f67349000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x00007f5f67046000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f5f66d40000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x00007f5f66b2a000)
	libracescreens.so => /usr/local/lib/torcs/lib/libracescreens.so 
(0x00007f5f66b18000)
	librobottools.so => /usr/local/lib/torcs/lib/librobottools.so 
(0x00007f5f66b0f000)
	libGL.so.1 => /usr/lib/nvidia-310/libGL.so.1 (0x00007f5f667ec000)
	libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x00007f5f664b2000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f5f68069000)
	libnvidia-tls.so.310.44 => /usr/lib/nvidia-310/tls/libnvidia-
tls.so.310.44 (0x00007f5f662ae000)
	libnvidia-glcore.so.310.44 => /usr/lib/nvidia-310/libnvidia-
glcore.so.310.44 (0x00007f5f63dbb000)
	libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 
(0x00007f5f63ba9000)
	libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 
(0x00007f5f6398a000)
	libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 
(0x00007f5f63786000)
	libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 
(0x00007f5f6357f000)


> No, not required, the only thing which needs some tweaking regarding 64 
> bit is plib (not part of TORCS itself), it must usually be compiled with 
> -fPIC 

Yes I compiled plib with -fPIC so I don't think its the issue either.


> You need first to change to the directory containing libtgf.so, see 
> output of "torcs -l" to locate it (or use find/file browser).

Ok, now the output is as you said 
nm libtgf.so | grep XML_ParserCreate
                 U XML_ParserCreate


> Btw. some other thought, if you are new to Linux, why are you using it 
> at all, what about using Windows for your work, would that be an option 
> (of course I encourage the use of Linux, but in the context of limited 
> time/fixed schedule it could make sense to use a familiar platform to 
> have less battles to fight...)?

Yeah, I agree that with Windows I would have had less trouble but I was told 
by my supervisor to do this in Linux. To be honest I have learned alot 
despite all the issues I have!

Also a poster below suggested that I run "ldd torcs-bin". It couldn't find 
some libraries like libtgf.so and libtgfclient.so all of them in the 
/usr/local/lib/torcs/lib directory so I added them to LD_LIBRARY_PATH. 
Unfortunately I still get the same error.

Again I thank you for your time and effort in helping me!

Hi Eugene

Can you post the output of "torcs -l"?
> Configure works as it should, no errors or anything. When I write "make" I
> get no errors as well. I also run it like this "make >& error.log" but
> search the file I can't find any errors. I didn't use any options either on
> configure or make(maybe I had to put something for 64bit there?).

No, not required, the only thing which needs some tweaking regarding 64 
bit is plib (not part of TORCS itself), it must usually be compiled with 
-fPIC (see 
http://torcs.sourceforge.net/index.php?name=Sections&op=viewarticle&artid=30#c2_3). 
But I guess (!) that's not the problem here.

> Here things get interesting as when I type the "nm libtgf.so | grep
> XML_ParserCreate" command in the terminal I get this :> nm: 'libtgf.so': No
> such file

You need first to change to the directory containing libtgf.so, see 
output of "torcs -l" to locate it (or use find/file browser).

> Unfortunately I didn't know exactly what to do with ld.so.conf, ldconfig and
> $LD_LIBRARY_PATH so I ran them in the terminal

Ok, sorry for the confusion:-)
- ldconfig: command to manage linker cache for ld.so (see "man ldconfig")
- ld.so.conf, configuration file, see also "man ldconfig"
- $LD_LIBRARY_PATH: Environment variable to adjust search for linked 
libraries, it is used as well in the "torcs" script (see around line 40).

> Being a Linux newbie thank you for taking the time to help me. I hope I gave
> some insight with what I wrote here.

Btw. some other thought, if you are new to Linux, why are you using it 
at all, what about using Windows for your work, would that be an option 
(of course I encourage the use of Linux, but in the context of limited 
time/fixed schedule it could make sense to use a familiar platform to 
have less battles to fight...)?

Best regards

Bernhard

Hi all,

Eugène,
When looking at the information you gave, I think your LD_LIBRARY_PATH does
not list all the lib directories of Torcs.

Basically, you just have to add it the "<prefix>/lib" dir of the prefix you
gave to the configure command.

Or you can list the libraries you are missing by doing a "ldd torcs-bin" on
the binary of Torcs (not the shell) and then adding all the paths of the
libraries it lists on the output to the LD_LIBRARY_PATH (only the
Torcs-specifics one).

Regards

--
Arnaud Ceyrolle
(depuis mon mobile)

Le 13 nov. 2013 19:36, "sp4m" <sp4...@mi...> a écrit :
>
> Hi Eugene
>
> Reading your emails, I'm wondering whether you have all the required
> dependencies installed.
>
> You don't specify *how* you install Torcs. Do you get the same error if
> you install Torcs via apt-get ?
>
> Best regards & good luck
> Chris
>
> On 11.11.2013 06:21, Evgenios Kastanias wrote:
> > Hi everyone.
> >
> > My final year project in University is to create AI for robots using
Torcs.
> >
> > However I cannot get it to start due to this error I keep getting.
> >
> > /usr/local/lib/torcs/torcs-bin: symbol lookup error:
> > /usr/local/lib/torcs/lib/libtgf.so: undefined symbol: XML_ParserCreate
> >
> >
> > I searched but I can't find anyone else with this error. I installed
torcs
> > from sources and followed the commands directly.
> >
> > I am using Ubuntu 13.04 64bit if it has a difference.
> >
> > I hope you can help me with this, and thanks for your time!
> >
> > Eugene
>
>
------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
>
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> Torcs-users mailing list
> Tor...@li...
> https://lists.sourceforge.net/lists/listinfo/torcs-users

I installed torcs from the all in one source package. I don't know if I 
missed and dependencies but wouldn't the configure script warn me to them? I 
didn't notice any errors. 

Thanks for your help in my problem!