View Full Version : Problems compiling

2004-08-17, 08:27
Excellent reply very informative and answered a lot of other questions I and
probarly other newbies to linux had. As you know I now have it working and
will test the production version when you have finished it. Thanks for all
your hard work and patience and I hope you are allowed to enter this plugin.


Dean Jackson

-----Original Message-----
From: discuss-bounces (AT) lists (DOT) slimdevices.com
[mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Jules Taplin
Sent: 17 August 2004 16:16
To: Slim Devices Discussion
Subject: [slim] Problems compiling

Ok Dean.

We can sort most of that out.

The first one ('should have a wav file in your directory') is the most
puzzling - if not told otherwise, then the xine libraries will simply
dump a file called 'xine-out.wav' into your current directory. The only
reason I can think of that it wouldn't is if you've been following some of
the other alienstream instructions (perhaps), and have a variable called
'XINE_WAVE_OUTPUT' set, which could be telling it to go somewhere else.

You can find out like this - type 'set' and press enter. That will list all
of the variables that are set in your shell. If you see one called
'XINE_WAVE_OUTPUT', then that's probably your problem. If that's the case,
then type 'unset XINE_WAVE_OUTPUT' and press enter to clear it. Then try

The reason that I said to do a './alienstream' is that this will ensure that

the version of alienstream you're running is the one in your current
directory ('.' is the shorthand for 'where I am'). Without the './' at the
end, the shell is left to either run one from your search path (explained
later), or to run the current directory version. So... it's safer to be
explicit in this case.

Your search path is a set of directories that are looked in when you try to
run something. If you type 'echo $PATH' into a shell, it'll return a string.

My one looks like this:

[jules@store Plugins]$ echo $PATH

This means that when you try to run something, it will look in
'/usr/local/bin/' first, followed by '/bin', followed by '/usr/bin',
followed by '/usr/X11R6/bin', followed by '/home/jules/bin'.

What those mean is probably worth some explanation - 'bin' stands for
'binaries' - or in better english 'runnable code'. Traditionally...
operators of UNIX machines use '/usr/local/bin/' for things they've added to

this local machine manually - that would be a good place to add things
yourself if you want all users to be able to use them.

'/bin'/ and '/usr/bin'. are similar, and the differences between them are
only interesting if you want to get into the internals (traditionally...
'/bin' executables are available earlier as machines are starting than
'/usr/bin/' ones). '/usr/X11R6/bin' contains executables that are important
for 'X11' (which is the base windowing system that UNIX's tend to use), and
'/home/jules/bin' is a path where you could stick binaries just for

As for the helper application - sorry - that's me being lazy with my
terminology - a 'helper' application is traditionally a program that's not
much use on it's own, but is important to make another one work. In this
case, we're talking about the program 'alienstream' which I supplied to you.

It's a helper, because it's not very interesting, but it's vital to alienBBC

working. ;)

From the look of your output - alienstream is almost certainly working, but

it's probably trying to write somewhere bad, which is why it falls over.

Does that help? If not... let me know exactly where you're hung up, and
we'll try to get you moved on.

I'm afraid that AlienBBC isn't quite 'production ready' on this version -
although it is shaping up to be quite good. Once we get it finished, it'll
be less painful than this, I promise ;)

-- Jules

----- Original Message -----
From: "dean" <dean (AT) packetradio (DOT) co.uk>
To: "'Slim Devices Discussion'" <discuss (AT) lists (DOT) slimdevices.com>
Sent: Tuesday, August 17, 2004 3:39 PM
Subject: [slim] Problems compiling

> Thanks got that bit working, now have another problem (yes sigh)
> Cant seem to get alienstream to run correctly?
> When I do the following
> [root@gateway slimserver]# ./alienstream
> http://www.bbc.co.uk/england/realmedia/live/localradio/threecounties.rpm
> mrl:
> 'http://www.bbc.co.uk/england/realmedia/live/localradio/threecounties.rpm'
> Connecting HTTP server... [0%]
> Buffering... [0%]
> rtsp://rmlivev8.bbc.net.uk/farm/*/ev7/live24/threecounties/live.ra
> Buffering... [0%]
> Message from Xine: Buffering... [100%]
> Stream finishedBuffering... [2%]
> Buffering... [4%]
> Buffering... [6%]
> And it will just sit there.
> I should end up with a wav file in this directory?, problem is I don't?
> Why do I have to do ./alienstream
> I followed the instructions but some clarification on the following would
> be
> helpful
> Put the alienstream helper application somewhere in your default system
> path.???
> What helper? How do I find out what my default system path is.
> I am fairly new to linux and am "slowly" figuring it out.
> I really want this to work and am really trying, I don't post till I have
> been stuck for at least 2 hours.
> Regards
> Dean Jackson
> -----Original Message-----
> From: discuss-bounces (AT) lists (DOT) slimdevices.com
> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Niek Jongerius
> Sent: 17 August 2004 06:33
> To: Slim Devices Discussion
> Subject: [slim] Problems compiling
> Hi Dean,
>> When I try to compile alienstream I get the following
>> [root@gateway /]# gcc34 -Wall -O2 `xine-config --cflags` `xine-config
>> --libs`-lX11 -L /usr/X11R6/lib -L /usr/local/lib -L /usr/local/lib/xine
>> -lm
>> -o alienstream alienstream.c
>> -bash: xine-config: command not found
>> -bash: xine-config: command not found
>> -bash: gcc34: command not found
>> [root@gateway /]#
>> so I tried to locate it
>> [root@gateway /]# locate xine-config
>> /usr/share/man/man1/xine-config.1.gz
>> /usr/bin/xine-config
>> but when I look /usr/bin I cannot see it?
>> Also searched for gcc34 but cant find that either?
> The "locate" command uses a database, which could be out-of-date. But
> that would imply you somehow removed it. Try "/usr/bin/xine-config"
> on the command line. You also should have the libs themselves. If you
> compiled them from source (which is necessary - you definitely want a
> recent version of xine libs for it to work properly) you should have
> xine files in /usr/local/lib. The "gcc34" can safely be replaced with
> "gcc". And finally there should be a space between the last back tick
> and the "-lX11" option.
> Regards, Niek.