From: Erwin, R. D <ric...@bo...> - 2003-01-13 05:17:54
|
Brian; Here is another bit of weirdness, when you do the "make install" --- # make install Making install in librtk make[1]: Entering directory `/scratch/librtk-2.1.1/librtk' Making install in . make[2]: Entering directory `/scratch/librtk-2.1.1/librtk' make[3]: Entering directory `/scratch/librtk-2.1.1/librtk' /bin/sh ../mkinstalldirs //librtk-2.1/lib .././install-sh -c -m 644 librtk.a //librtk-2.1/lib/librtk.a ranlib //librtk-2.1/lib/librtk.a /bin/sh ../mkinstalldirs //librtk-2.1/include .././install-sh -c -m 644 rtk.h //librtk-2.1/include/rtk.h make[3]: Leaving directory `/scratch/librtk-2.1.1/librtk' make[2]: Leaving directory `/scratch/librtk-2.1.1/librtk' make[1]: Leaving directory `/scratch/librtk-2.1.1/librtk' Making install in test make[1]: Entering directory `/scratch/librtk-2.1.1/test' make[2]: Entering directory `/scratch/librtk-2.1.1/test' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/scratch/librtk-2.1.1/test' make[1]: Leaving directory `/scratch/librtk-2.1.1/test' Making install in pyrtk make[1]: Entering directory `/scratch/librtk-2.1.1/pyrtk' make[2]: Entering directory `/scratch/librtk-2.1.1/pyrtk' make[2]: Nothing to be done for `install-exec-am'. make install-data-hook make[3]: Entering directory `/scratch/librtk-2.1.1/pyrtk' make[3]: Nothing to be done for `install-data-hook'. make[3]: Leaving directory `/scratch/librtk-2.1.1/pyrtk' make[2]: Leaving directory `/scratch/librtk-2.1.1/pyrtk' make[1]: Leaving directory `/scratch/librtk-2.1.1/pyrtk' make[1]: Entering directory `/scratch/librtk-2.1.1' make[2]: Entering directory `/scratch/librtk-2.1.1' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/scratch/librtk-2.1.1' make[1]: Leaving directory `/scratch/librtk-2.1.1' Why doesn't this stuff default-install in /usr/local/*, and what do we = do to ensure it? If we can't, how do we know for sure where what goes = in /usr/local? Thanks, Rich Erwin Boeing SSG - M&CT Support (425) 865-3414 -----Original Message----- From: brian gerkey [mailto:bg...@us...] Sent: Sunday, January 12, 2003 5:10 PM To: Erwin, Richard D Cc: pla...@li... Subject: Re: [Playerstage-users] FW: librtk build problems On Sun, 12 Jan 2003, Erwin, Richard D wrote: > > > Folks; > > > > I'm a newbie to rtklib/player/stage, and am failing to get a build = of rtklib to happen. > > > > I'm using 2.1.1, and I've tried Python 2.2 on a Solaris 8 box (shown = below) and Python 1.5 on a Solaris 6 box. I'm also using gmake 3.79. > > > > Any advice you can provide would be most appreciated. > > hi Rich, The problem is that the ffmpeg library, which librtk uses to make = movies, doesn't build on many platforms (including Solaris), resulting in this = error: > cd ../ffmpeg && ./configure && make > ./configure: bad substitution > make[3]: *** [buildffmpeg] Error 1 I'll put a note on the FAQ about this issue, since several people have reported it. The short-term solution is for you to pass '--without-libavcodec' to = librtk's 'configure' script before building. That way ffmpeg won't be built. Of course, you won't be able to make movies of Stage simulations. The long-term solution is for us to either make ffmpeg more portable or = select a different animation library to use. Stay tuned. brian. |
From: David J. N. <dn...@i-...> - 2003-01-13 08:54:01
|
Rich Try using the --prefix=/usr/local/player with the configure script.This will generate makefiles with a default install location of /usr/local/player. BTW this also applies to stage and librtk as well (but change the prefix to the appropriate directory). Dave Naffin PhD Student RESL Dept of Comp Sci University of Southern California ---Original Message------------- Brian; Here is another bit of weirdness, when you do the "make install" --- # make install Making install in librtk make[1]: Entering directory `/scratch/librtk-2.1.1/librtk' Making install in . make[2]: Entering directory `/scratch/librtk-2.1.1/librtk' make[3]: Entering directory `/scratch/librtk-2.1.1/librtk' /bin/sh ../mkinstalldirs //librtk-2.1/lib .././install-sh -c -m 644 librtk.a //librtk-2.1/lib/librtk.a ranlib //librtk-2.1/lib/librtk.a /bin/sh ../mkinstalldirs //librtk-2.1/include .././install-sh -c -m 644 rtk.h //librtk-2.1/include/rtk.h make[3]: Leaving directory `/scratch/librtk-2.1.1/librtk' make[2]: Leaving directory `/scratch/librtk-2.1.1/librtk' make[1]: Leaving directory `/scratch/librtk-2.1.1/librtk' Making install in test make[1]: Entering directory `/scratch/librtk-2.1.1/test' make[2]: Entering directory `/scratch/librtk-2.1.1/test' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/scratch/librtk-2.1.1/test' make[1]: Leaving directory `/scratch/librtk-2.1.1/test' Making install in pyrtk make[1]: Entering directory `/scratch/librtk-2.1.1/pyrtk' make[2]: Entering directory `/scratch/librtk-2.1.1/pyrtk' make[2]: Nothing to be done for `install-exec-am'. make install-data-hook make[3]: Entering directory `/scratch/librtk-2.1.1/pyrtk' make[3]: Nothing to be done for `install-data-hook'. make[3]: Leaving directory `/scratch/librtk-2.1.1/pyrtk' make[2]: Leaving directory `/scratch/librtk-2.1.1/pyrtk' make[1]: Leaving directory `/scratch/librtk-2.1.1/pyrtk' make[1]: Entering directory `/scratch/librtk-2.1.1' make[2]: Entering directory `/scratch/librtk-2.1.1' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/scratch/librtk-2.1.1' make[1]: Leaving directory `/scratch/librtk-2.1.1' Why doesn't this stuff default-install in /usr/local/*, and what do we do to ensure it? If we can't, how do we know for sure where what goes in /usr/local? Thanks, Rich Erwin Boeing SSG - M&CT Support (425) 865-3414 |
From: Richard V. <va...@hr...> - 2003-01-13 17:35:39
|
All the P/S tools install by default in $HOME rather than /usr/local because many users do not have root access to their hosts. By default, *nothing* goes into /usr/local. To redirect the install use: ./configure --prefix=/usr/local/player before building. "--prefix" is a standard switch for packages managed by autoconf, and is described in FAQ number 3: http://playerstage.sourceforge.net/faq.html#player_install Thanks for reminding us to address the problem with ffmpeg not building out of the box. While we're figuring out a fix we'll make sure it's disabled by default on platforms we know are broken. It's really helpful to hear from a Solaris-based user - please keep in touch and let us know if you're still having trouble. Cheers, Richard. On Sun, 12 Jan 2003, Erwin, Richard D wrote: > Brian; > > Here is another bit of weirdness, when you do the "make install" --- > > # make install > Making install in librtk > make[1]: Entering directory `/scratch/librtk-2.1.1/librtk' > Making install in . > make[2]: Entering directory `/scratch/librtk-2.1.1/librtk' > make[3]: Entering directory `/scratch/librtk-2.1.1/librtk' > /bin/sh ../mkinstalldirs //librtk-2.1/lib > .././install-sh -c -m 644 librtk.a //librtk-2.1/lib/librtk.a > ranlib //librtk-2.1/lib/librtk.a > /bin/sh ../mkinstalldirs //librtk-2.1/include > .././install-sh -c -m 644 rtk.h //librtk-2.1/include/rtk.h > make[3]: Leaving directory `/scratch/librtk-2.1.1/librtk' > make[2]: Leaving directory `/scratch/librtk-2.1.1/librtk' > make[1]: Leaving directory `/scratch/librtk-2.1.1/librtk' > Making install in test > make[1]: Entering directory `/scratch/librtk-2.1.1/test' > make[2]: Entering directory `/scratch/librtk-2.1.1/test' > make[2]: Nothing to be done for `install-exec-am'. > make[2]: Nothing to be done for `install-data-am'. > make[2]: Leaving directory `/scratch/librtk-2.1.1/test' > make[1]: Leaving directory `/scratch/librtk-2.1.1/test' > Making install in pyrtk > make[1]: Entering directory `/scratch/librtk-2.1.1/pyrtk' > make[2]: Entering directory `/scratch/librtk-2.1.1/pyrtk' > make[2]: Nothing to be done for `install-exec-am'. > make install-data-hook > make[3]: Entering directory `/scratch/librtk-2.1.1/pyrtk' > make[3]: Nothing to be done for `install-data-hook'. > make[3]: Leaving directory `/scratch/librtk-2.1.1/pyrtk' > make[2]: Leaving directory `/scratch/librtk-2.1.1/pyrtk' > make[1]: Leaving directory `/scratch/librtk-2.1.1/pyrtk' > make[1]: Entering directory `/scratch/librtk-2.1.1' > make[2]: Entering directory `/scratch/librtk-2.1.1' > make[2]: Nothing to be done for `install-exec-am'. > make[2]: Nothing to be done for `install-data-am'. > make[2]: Leaving directory `/scratch/librtk-2.1.1' > make[1]: Leaving directory `/scratch/librtk-2.1.1' > > Why doesn't this stuff default-install in /usr/local/*, and what do we do to ensure it? If we can't, how do we know for sure where what goes in /usr/local? > > Thanks, > Rich Erwin > Boeing SSG - M&CT Support > (425) 865-3414 > > > > -----Original Message----- > From: brian gerkey [mailto:bg...@us...] > Sent: Sunday, January 12, 2003 5:10 PM > To: Erwin, Richard D > Cc: pla...@li... > Subject: Re: [Playerstage-users] FW: librtk build problems > > > On Sun, 12 Jan 2003, Erwin, Richard D wrote: > > > > > > Folks; > > > > > > I'm a newbie to rtklib/player/stage, and am failing to get a build of rtklib to happen. > > > > > > I'm using 2.1.1, and I've tried Python 2.2 on a Solaris 8 box (shown below) and Python 1.5 on a Solaris 6 box. I'm also using gmake 3.79. > > > > > > Any advice you can provide would be most appreciated. > > > > > hi Rich, > > The problem is that the ffmpeg library, which librtk uses to make movies, > doesn't build on many platforms (including Solaris), resulting in this error: > > > cd ../ffmpeg && ./configure && make > > ./configure: bad substitution > > make[3]: *** [buildffmpeg] Error 1 > > I'll put a note on the FAQ about this issue, since several people have > reported it. > > The short-term solution is for you to pass '--without-libavcodec' to librtk's > 'configure' script before building. That way ffmpeg won't be built. Of > course, you won't be able to make movies of Stage simulations. > > The long-term solution is for us to either make ffmpeg more portable or select > a different animation library to use. Stay tuned. > > brian. > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld http://www.vasoftware.com > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > -- Richard Vaughan Information Sciences Lab, HRL Laboratories LLC. va...@hr... (310) 317-5689 |