Re: Compiling gnuplot with libgd
- From: psummers@xxxxxxxxxxxx
- Date: Thu, 13 Sep 2007 08:42:38 -0700
Hans-Bernhard Bröker wrote:
psummers@xxxxxxxxxxxx wrote:
maybe the compiler directive should be:
g++ -g -O2 LDFLAGS=-L/opt/gnuplot/lib -o gnuplot alloc.o axis.o
breaders.o ect..
NO.
#!/bin/bash
export LD_LIBRARY_PATH="/opt/gnuplot/lib:$LD_LIBRARY_PATH"
exec /opt/gnuplot/bin/gnuplot
The correct solution to this is that you should make this modification
of LD_LIBRARY_PATH permanently and globally, not just for the duration
of running this script.
A .so library that is not in the ld.so library search path is
essentially unusable. That's the corner you painted yourself into.
Hi,
The application I am building is a turnkey display board for
production statistics. It needs to run on abandoned and scavenged
hardware and needs minimal support. Basically this means booting the
operating system off a cdrom, installing the gnuplot graphing program
and running a script that monitors a directory and displays the
uploaded statistics from that directory.
To do this I use a version of linux that will run without a hardrive
in 64Meg of RAM booting in livecd cdrom (or 64Meg Compact Flash) mode.
By building a package for damn small linux I can have it automatically
install gnuplot and run my required script without having to customize
the bootcd or operating system.
Basically this is a tool that assist me in my job and I have no time
to support it. If something goes wrong I can just reboot the machine.
It will automatically restart, no hard disk failures to worry about,
nothing is saved so I don't have to worry about corruption.
This imposes some limitations on the file system if I want to minimize
RAM usage as the filesystem exists in RAM and CDROM. This is the
tradeoff I chose to make so I could devote my meager budget to get the
biggest LCDs I could afford (we made a $300,000 loss last month).
Currently the script method is working reliably for me. It's not
perfect but is a limitation that other damn small linux users have
come to live with. It enables me to complete my project and to return
the gnuplot extension to the rest of the damnsmalllinux community in a
package format that someone else can use
In two weeks, I have learned how to build and burn a linux livecd that
boots up in a full developement system, compile gnuplot with graphics
library support, build some basic graphing scripts, put gnuplot into a
self installing package with custom desktop icon and should run
without any support. My first attempt was using open office to
generate the graphs but the hardware requirements were too high.
I barely know anything beyond, ./configure, make, make install so
everything I have acheived is due to the help and advice of yourself
and others in this and the damn small linux forum. There are enormous
gaps in my knowledge and I am really just joining-the-dots. I don't
really understand what is going on between them.
Regards Phil
.
- Follow-Ups:
- Re: Compiling gnuplot with libgd
- From: Martin Mohr
- Re: Compiling gnuplot with libgd
- References:
- Compiling gnuplot with libgd
- From: psummers
- Re: Compiling gnuplot with libgd
- From: Hans-Bernhard Bröker
- Re: Compiling gnuplot with libgd
- From: psummers
- Re: Compiling gnuplot with libgd
- From: Hans-Bernhard Bröker
- Compiling gnuplot with libgd
- Prev by Date: Bug? Changing the values of variables within the "plot" command
- Next by Date: Re: missing symbols in latex driver
- Previous by thread: Re: Compiling gnuplot with libgd
- Next by thread: Re: Compiling gnuplot with libgd
- Index(es):
Relevant Pages
|