gnuplot development

On Sunday 29 November 2009, Shigeharu TAKENO wrote:
> shige 11/30 2009
> ----------------
> 
> In term/gd.trm of version 4.4.0-rc1
> 
>  $Id: gd.trm,v 1.136.2.8 2009/10/06 23:03:39 sfeam Exp $
> 
> I found the following point. 

???
Very strange.
I wonder how those two lines went missing?

	thanks!



> ----- From here -----
> --- gd.trm.ORG	2009-10-07 08:03:39.000000000 +0900
> +++ gd.trm	2009-11-30 16:06:02.000000000 +0900
> @@ -2568,6 +2568,7 @@
>  "              {tiny | small | medium | large | giant}",
>  "              {font \"<face> {,<pointsize>}\"} {{no}enhanced}",
>  "              {size <x>,<y>} {{no}crop}",
> +"              {animate {delay <d>} {loop <n>} {{no}optimize}}",
>  "              {<color0> <color1> <color2> ...}",
>  "",
>  " PNG, JPEG and GIF images are created using the external library libgd.",
> @@ -2601,6 +2602,7 @@
>  " the creation of animated gifs. The default delay between display of",
>  " successive images may be specified in units of 1/100 second (default 5).",
>  " The actual delay may vary depending on the program used as a viewer.",
> +" Number of animation loops can be specified, default 0 means infinity.",
>  " An animation sequence is terminated by the next `set output` or `set term`",
>  " command.  The `optimize` option has two effects on the animation.",
>  "",
> ----- To here -----
> 
> +========================================================+
>  Shigeharu TAKENO     NIigata Institute of Technology
>                        kashiwazaki,Niigata 945-1195 JAPAN
>  shige@...   TEL(&FAX): +81-257-22-8161
> +========================================================+
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> gnuplot-beta mailing list
> gnuplot-beta@...
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>

On Monday 30 November 2009 02:57:27 Tatsuro MATSUOKA wrote:
> Hello
> 
> In the src/Makefile.in after ./prepare, I found.
> 
> @BUILD_LUA_TRUE@... = gnuplot-tikz.lua$(EXEEXT)
> 
> I hear that gnuplot-tikz.lua is a script so that $(EXEEXT) is harmful for cygwin build.
> For cygwin  $(EXEEXT) is '.exe', this makes unhappy results in cygwin.
> For real unix $(EXEEXT) is empty so that error not occurred accidentally.
> 
> I think that 'gnuplot-tikz.lua$(EXEEXT)' should be 'gnuplot-tikz.lua'.
> 
> I am not familiar with autotools so that I cannot figure out where should I modify to remove it. 

Yes, this is a problem with autotools.
Because the file is installed in $libexecdir, the autotools think it is an executable
and therefore they add the extension $(EXEEXT).
I am not an autotools expert, but I see no way to turn this off for only a single file.

The only thing I can think of is to install the file somewhere else entirely.  But where?

Because it is related to LaTeX, it might logically be installed into a latex directory.
Unfortunately, people are reporting problems with the latex installation directories also.
So I don't think that would help in practice.

Or we could create another subdirectory under /usr/local/share/gnuplot/VERSION/
We alread have subdirectories for javascript and PostScript, so adding one for
lua scripts seems reasonable.  But the lua.trm source code will have to be changed also,
so that it knows where to look for the script file.   I will attempt to create a patch.

	Ethan




> BTW, after removing $(EXEEXT) form @BUILD_LUA_TRUE@... = gnuplot-tikz.lua$(EXEEXT) in
> Makefile.in, make goes well.
> 
> However, there occured error at make install-strip
> 
>   /bin/sh /cygdrive/d/usr/Tatsu/cyghome-1.7/gnuplotcvs/gnuplot/install-sh -c -s gnuplot-tikz.lua
> '/usr/local/libexec/gnuplot/4.5/./gnuplot-tikz.lua.exe'
> strip:/usr/local/libexec/gnuplot/4.5/./_inst.12112_: File format not recognized
> make[4]: *** [install-pkglibexecPROGRAMS] Error
> 
> Where can I found another gnuplot-tikz.lua$(EXEEXT) for make install?
> 
> Please give me advises.
> 
> Regards
> 
> Tatsuro



-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle 98195-7742

Ethan Merritt wrote:

> Yes, this is a problem with autotools.

Actually, it's more a problem with how we use them.

> Because the file is installed in $libexecdir, the autotools think it is an executable
> and therefore they add the extension $(EXEEXT).

No.  It thinks so because we told it so, by listing gnuplot-tikz.lua in 
gnuplotlibexec_PROGRAMS.  It's the _PROGRAMS part that makes this a 
presumed binary executable, and causes $(EXEEXT) to be added to its name.

To me it looks like the lua section in src/Makefile.am should just be

pkglibexec_SCRIPTS =
if BUILD_LUA
pkglibexec_SCRIPTS += gnuplot-tikz.lua
endif

(or possibly that should be dist_pkglibexec_SCRIPTS) For the details see 
"info automake other scripts".

Strictly speaking scripts shouldn't go to $libexecdir, nor a 
subdirectory of it, like our $pkglibexecdir.  They belong in the 
platform-independent directories, e.g. $pkgdatadir.  That way, even if 
you install to a $prefix shared by multiple binary architectures, you 
would still only copy of them.

Hello Han and Ethan

Thank you for your helpful comments.

> To me it looks like the lua section in src/Makefile.am should just be
> 
> pkglibexec_SCRIPTS =
> if BUILD_LUA
> pkglibexec_SCRIPTS += gnuplot-tikz.lua
> endif
> 

The above was successful to remove  $(EXEEXT) from gnuplot-tikz.lua$(EXEEXT).

However

make
make[3]: *** No rule to make target `gnuplot-tikz.lua', needed by `all-am'.  Stop.
make[3]: Leaving directory `/cygdrive/d/usr/Tatsu/cyghome-1.7/gnuplotcvs/gnuplot/src'
make[2]: [all-recursive] Error 1 (ignored)

make install-strip
make[3]: *** No rule to make target `gnuplot-tikz.lua', needed by `all-am'.  Stop.

Perhaps I have to tweak the below.
> (or possibly that should be dist_pkglibexec_SCRIPTS) For the details see 
> "info automake other scripts".

At the moment I manually copy and strip gnuplot.exe and gnuplot_x11.exe which have not been installed
by make install-strip from the side effect of the error above.

Ethan>
>Or we could create another subdirectory under /usr/local/share/gnuplot/VERSION/
>We already have subdirectories for javascript and PostScript, so adding one for
>lua scripts seems reasonable.  But the lua.trm source code will have to be changed also,
>so that it knows where to look for the script file.   I will attempt to create a patch.

I temporarily  put the script 'gnuplot-tikz.lua' to  /usr/local/libexec/gnuplot/4.5/.
I will wait for your patch.

Regards

Tatsuro

--- Hans-Bernhard Br将モker  wrote:

> Ethan Merritt wrote:
> 
> > Yes, this is a problem with autotools.
> 
> Actually, it's more a problem with how we use them.
> 
> > Because the file is installed in $libexecdir, the autotools think it is an executable
> > and therefore they add the extension $(EXEEXT).
> 
> No.  It thinks so because we told it so, by listing gnuplot-tikz.lua in 
> gnuplotlibexec_PROGRAMS.  It's the _PROGRAMS part that makes this a 
> presumed binary executable, and causes $(EXEEXT) to be added to its name.
> 
> To me it looks like the lua section in src/Makefile.am should just be
> 
> pkglibexec_SCRIPTS =
> if BUILD_LUA
> pkglibexec_SCRIPTS += gnuplot-tikz.lua
> endif
> 
> (or possibly that should be dist_pkglibexec_SCRIPTS) For the details see 
> "info automake other scripts".
> 
> Strictly speaking scripts shouldn't go to $libexecdir, nor a 
> subdirectory of it, like our $pkglibexecdir.  They belong in the 
> platform-independent directories, e.g. $pkgdatadir.  That way, even if 
> you install to a $prefix shared by multiple binary architectures, you 
> would still only copy of them.
> 
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing. 
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> gnuplot-beta mailing list
> gnuplot-beta@...
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 



--------------------------------------
Learn more about HIV/AIDS - Red Ribbon Campaign 2009
http://pr.mail.yahoo.co.jp/redribbon/

On Monday 30 November 2009 14:42:27 Hans-Bernhard Bröker wrote:

> Strictly speaking scripts shouldn't go to $libexecdir, nor a 
> subdirectory of it, like our $pkglibexecdir.  They belong in the 
> platform-independent directories, e.g. $pkgdatadir.

I have uploaded a patchset to SourceForge that changes the installation
directory to $pkgdatadir/lua.
This is parallel to the way we already handle scripts used by the canvas
and postscript terminals.

-- 
Ethan A Merritt

Hello

I have now finished to build gnuplot 4.5 (cvs) with lua and tikz terminals.
All processes ./configure, make, make check, and make install-strip were successfully carried out!!
No errors!! Fine!!

Thank you for your efforts

Regards

Tatsuro


--------------------------------------
Learn more about HIV/AIDS - Red Ribbon Campaign 2009
http://pr.mail.yahoo.co.jp/redribbon/

Hello 

I have forget one thing.
For build on MinGW, I have to begin with building the lua.

I will report afterwards.

Thank you for your preparing a new makefile for lua.

Regards

Tatsuro



--- Tatsuro MATSUOKA wrote:

> Hello
> 
> I have now finished to build gnuplot 4.5 (cvs) with lua and tikz terminals.
> All processes ./configure, make, make check, and make install-strip were successfully carried
> out!!
> No errors!! Fine!!
> 
> Thank you for your efforts
> 
> Regards
> 
> Tatsuro
> 
> 
> --------------------------------------
> Learn more about HIV/AIDS - Red Ribbon Campaign 2009
> http://pr.mail.yahoo.co.jp/redribbon/
> 


--------------------------------------
Learn more about HIV/AIDS - Red Ribbon Campaign 2009
http://pr.mail.yahoo.co.jp/redribbon/

> BTW, I have a quick look it and found that the document 'ReadmeWindows' 
> lacks explanation of 'gnuplot.exe'.  This is one of the important topic of 
> gnuplot 4.4.

Thanks for spotting this. I propose the following text:

gnuplot.exe: Text (console) mode version of the gnuplot executable with all
the associated pipe functionality as it is usual on all other platforms.
This means that this program can also accept commands on stdin (standard
input) and print messages on stdout (standard output). This program replaces
pgnuplot.exe and it is recommended to use it for 3rd party applications
using gnuplot as graph engine, for example Octave (www.octave.org).

Feel free to comment/update.

---
PM

Hello


--- Petr Mikulik  wrote:

> 
> Thanks for spotting this. I propose the following text:
> 
> gnuplot.exe: Text (console) mode version of the gnuplot executable with all
> the associated pipe functionality as it is usual on all other platforms.
> This means that this program can also accept commands on stdin (standard
> input) and print messages on stdout (standard output). This program replaces
> pgnuplot.exe and it is recommended to use it for 3rd party applications
> using gnuplot as graph engine, for example Octave (www.octave.org).
> 
> Feel free to comment/update.

I think that this is a good explanation.
I vote it

Tasturo

--------------------------------------
Learn more about HIV/AIDS - Red Ribbon Campaign 2009
http://pr.mail.yahoo.co.jp/redribbon/

On Monday 30 November 2009 02:34:12 Tatsuro MATSUOKA wrote:
> Hello
> 
> In the http://sourceforge.net/projects/gnuplot/files/gnuplot/4.4.0-rc1/announce.4.4/view 
> 
> I have found.
> 
> ********
> The phrase of 'wxt as the default interactive terminal' is found, however no description of the wxt
> terminal in the document NEWS.
> 
> Is this a mistake? Or is there any reason that the description of the wxt terminal is omitted from the
> NEWS.

NEWS is intended to be a list of changes and new features that are
present in 4.4 but not in 4.2

But the wxt terminal is already present in 4.2, so it is not "new".


-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle 98195-7742

On Sat, 28 Nov 2009, Ethan Merritt wrote:

> On Saturday 28 November 2009, Allin Cottrell wrote:
> >
> > On Sat, 28 Nov 2009, Ethan Merritt wrote:
> >
> > > On Saturday 28 November 2009, Allin Cottrell wrote:
> > > >
> > > > I'm not sure what's going on under cygwin, but this is a bit
> > > > tricky on Linux.  Gnuplot uses pkg-config to test for lua, but a
> > > > stock installation of lua-5.1.4 using "make linux install" does
> > > > not install the lua.pc file.
> > >
> > > Eh?  It installs normally for me.  The *.pc ends up here:
> > >    /usr/lib/pkgconfig/lua.pc
> > >
> > > lua -v
> > > Lua 5.1.4  Copyright (C) 1994-2008 Lua.org, PUC-Rio
> >
> > Tarball from http://www.lua.org/ftp/lua-5.1.4.tar.gz
> >
> > allin@...$ make linux
> > [no errors, all looks fine]
> > allin@...$ make -n linux install
> > cd src && make linux
> > make[1]: Entering directory `/home/allin/lua-5.1.4/src'
> > make all MYCFLAGS=-DLUA_USE_LINUX MYLIBS="-Wl,-E -ldl -lreadline
> > -lhistory -lncurses"
> > make[2]: Entering directory `/home/allin/lua-5.1.4/src'
> > make[2]: Nothing to be done for `all'.
> > make[2]: Leaving directory `/home/allin/lua-5.1.4/src'
> > make[1]: Leaving directory `/home/allin/lua-5.1.4/src'
> > cd src && mkdir -p /usr/local/bin /usr/local/include
> > /usr/local/lib /usr/local/man/man1 /usr/local/share/lua/5.1
> > /usr/local/lib/lua/5.1
> > cd src && install -p -m 0755 lua luac /usr/local/bin
> > cd src && install -p -m 0644 lua.h luaconf.h lualib.h lauxlib.h
> > ../etc/lua.hpp /usr/local/include
> > cd src && install -p -m 0644 liblua.a /usr/local/lib
> > cd doc && install -p -m 0644 lua.1 luac.1 /usr/local/man/man1
> >
> > And that's it; no .pc file.  If you got something to go into
> > /usr/lib/pkgconfig (note, not under /usr/local, which is the
> > default), you're doing something special.
>
> I started with a distribution source package:
>   lua-5.1.4-6mdv2009.1.src.rpm
>
> I suppose Mandriva may have fixed it, although I don't see a notice to
> that effect.

I think we can assume that Mandriva fixed it, since the original
does not install the (broken) pc file.

Allin Cottrell

On Sat, 28 Nov 2009, Ethan Merritt wrote:

> I gave up on [kpsepand] ages ago.  kpsexpand is terminally
> broken on all my machines.  No idea how it's supposed to work,
> but clearly it doesn't.  That's why it's disabled by default in
> configure.in.

It's disabled for "run-time" use (I'm not sure what that would
involve) but it's used willy nilly in the Makefile for
share/LaTeX, and I would say it's misused in that context.

Allin Cottrell

On Sun, 29 Nov 2009, Mojca Miklavec wrote:

> The following definitely doesn't
> work for me:
>      kpsexpand '$$TEXMF'
> but
>     kpsexpand "\$TEXMF"
> does...

Bear in mind that the "$$..." formulation occurs in a Makefile,
where it is correct.  "\$" gives the equivalent protection to
"$" in regular shell usage.

Allin Cottrell

Hello

Sorry for my duplicated post.

Does anyone explain the behavior below?

Regards

Tatsuro


--- Tatsuro MATSUOKA wrote:

> Sorry for my successive post.
> 
> I have looked at the config.log:
> 
> configure:8273: checking for LUA
> configure:8281: $PKG_CONFIG --exists --print-errors "lua"
> configure:8284: $? = 0
> configure:8299: $PKG_CONFIG --exists --print-errors "lua"
> configure:8302: $? = 0
> configure:8340: result: yes
> configure:8353: checking for library containing luaL_openlibs
> configure:8384: gcc-4 -o conftest.exe -O3 -fomit-frame-pointer   -I/usr/include  -L/usr/lib
> conftest.c
>  -llua -lm   >&5
> configure:8384: $? = 0
> configure:8401: result: none required
> configure:8411: checking lua.h usability
> configure:8411: gcc-4 -c -O3 -fomit-frame-pointer   -I/usr/include conftest.c >&5
> configure:8411: $? = 0
> configure:8411: result: yes
> configure:8411: checking lua.h presence
> configure:8411: gcc-4 -E   -I/usr/include conftest.c
> configure:8411: $? = 0
> configure:8411: result: yes
> configure:8411: checking for lua.h
> configure:8411: result: yes
> 
> *****************
> configure:8384: gcc-4 -o conftest.exe -O3 -fomit-frame-pointer   -I/usr/include  -L/usr/lib
> conftest.c
>  -llua -lm   >&5
> configure:8384: $? = 0
> configure:8401: result: none required
> ***************
>  $? = 0 but result: none required
> ????
> What is caused? I'm now in confusion.
> 
> Regards
> 
> Tatsuro
> 
> --- Tatsuro MATSUOKA <tmacchant3@...> wrote:
> 
> > Hello
> > 
> > --- Tatsuro MATSUOKA  wrote:
> > 
> > Ah! I have overlooked one points.
> > > ./configure
> > >  :
> > > checking for LUA... yes
> > > checking for library containing luaL_openlibs... none required
> > > checking lua.h usability... yes
> > > checking lua.h presence... yes
> > > checking for lua.h... yes
> > >  :
> > >   lua/TikZ terminal: yes
> > >  :
> > >   TeX *.sty for lua/tikz terminal: yes
> > > 
> > > In config.h after configure, I can see,
> > > 
> > > /* Define if you want the lua/TikZ terminal. */
> > > #define HAVE_LUA 1
> > > 
> > ************
> > > checking for library containing luaL_openlibs... none required
> > ************
> > 
> > The above might be an origin of my failure.  I have check cygwin setup concerning the lua.
> > 
> > Regards
> > 
> > Tatsuro 
> > 
> > --------------------------------------
> > What is your No.1 Entertainment of 2009? -Yahoo! JAPAN Net BANZUKE 2009
> > http://pr.mail.yahoo.co.jp/banzuke/
> > 
> 
> 
> --------------------------------------
> What is your No.1 Entertainment of 2009? -Yahoo! JAPAN Net BANZUKE 2009
> http://pr.mail.yahoo.co.jp/banzuke/
> 


--------------------------------------
What is your No.1 Entertainment of 2009? -Yahoo! JAPAN Net BANZUKE 2009
http://pr.mail.yahoo.co.jp/banzuke/

On Mon, 30 Nov 2009, Tatsuro MATSUOKA wrote:

> Does anyone explain the behavior below?
> >
> > I have looked at the config.log:
> >
> > configure:8273: checking for LUA
> > configure:8281: $PKG_CONFIG --exists --print-errors "lua"
> > configure:8284: $? = 0
> > configure:8299: $PKG_CONFIG --exists --print-errors "lua"
> > configure:8302: $? = 0
> > configure:8340: result: yes
> > configure:8353: checking for library containing luaL_openlibs
> > configure:8384: gcc-4 -o conftest.exe -O3 -fomit-frame-pointer   -I/usr/include  -L/usr/lib
> > conftest.c
> >  -llua -lm   >&5
> > configure:8384: $? = 0
> > configure:8401: result: none required

> >  $? = 0 but result: none required
> > ????
> > What is caused? I'm now in confusion.

This seems to be "normal".  In my config.log I have

configure:12504: checking for library containing luaL_openlibs
configure:12545: gcc -o conftest -g -O2   -I/usr/X11R7/include
-I/usr/local/include -I/usr/local/include  -L/usr/lib -L/usr/X11R7/lib
-L/usr/local/lib conftest.c -lm  -L/usr/local/lib -llua -lm -ldl >&5
configure:12552: $? = 0
configure:12583: result: none required

But this doesn't seem to be a problem: "make" builds a gnuplot
binary that supports lua/tikz OK.

Allin Cottrell

On Sunday 29 November 2009, Tatsuro MATSUOKA wrote:
> Hello
> 
> Sorry for my duplicated post.
> 
> Does anyone explain the behavior below?
> 
> Regards
> 
> Tatsuro
> 
> 
> --- Tatsuro MATSUOKA wrote:
> 
> > Sorry for my successive post.
> > 
> > I have looked at the config.log:
> > 
> > configure:8273: checking for LUA
> > configure:8281: $PKG_CONFIG --exists --print-errors "lua"
> > configure:8284: $? = 0
> > configure:8299: $PKG_CONFIG --exists --print-errors "lua"
> > configure:8302: $? = 0
> > configure:8340: result: yes
> > configure:8353: checking for library containing luaL_openlibs
> > configure:8384: gcc-4 -o conftest.exe -O3 -fomit-frame-pointer   -I/usr/include  -L/usr/lib
> > conftest.c
> >  -llua -lm   >&5
> > configure:8384: $? = 0
> > configure:8401: result: none required
> > configure:8411: checking lua.h usability
> > configure:8411: gcc-4 -c -O3 -fomit-frame-pointer   -I/usr/include conftest.c >&5
> > configure:8411: $? = 0
> > configure:8411: result: yes
> > configure:8411: checking lua.h presence
> > configure:8411: gcc-4 -E   -I/usr/include conftest.c
> > configure:8411: $? = 0
> > configure:8411: result: yes
> > configure:8411: checking for lua.h
> > configure:8411: result: yes
> > 
> > *****************
> > configure:8384: gcc-4 -o conftest.exe -O3 -fomit-frame-pointer   -I/usr/include  -L/usr/lib
> > conftest.c
> >  -llua -lm   >&5
> > configure:8384: $? = 0
> > configure:8401: result: none required
> > ***************
> >  $? = 0 but result: none required
> > ????
> > What is caused? I'm now in confusion.

I cannot help with cygwin.
But the message above is not an error. I get the same report
when building successfully under linux.  

configure:12416: checking for LUA
configure:12483: result: yes
configure:12442: $PKG_CONFIG --exists --print-errors "lua"
configure:12445: $? = 0
configure:12483: result: yes
configure:12496: checking for library containing luaL_openlibs
configure:12537: gcc -o conftest -g -O2   -I/usr/local/include   -L/usr/X11R6/lib  conftest.c -lm  -llua -lm   >&5
configure:12544: $? = 0
configure:12575: result: none required
configure:12601: checking lua.h usability
configure:12618: gcc -c -g -O2   -I/usr/local/include  conftest.c >&5
configure:12625: $? = 0
configure:12639: result: yes

I think this means that the test program created by the configure
script compiles and links correctly without requiring any extra libraries.

I do notice a difference in the two configure logs, however.
It seems from your log that the test for lua.h comes first, and then lua libraries second.
My log shows first a test for the libraries and then a test for lua.h
So the configure script may be different for some reason.


	Ethan

Hello Ethan and Allin

Configure itself seems to be OK.

Then I will look into 'make' process and the Makefile  to seek the origin of the failure.

Thanks a lot!!

Regards

Tatsuro



--- Ethan Merritt wrote:

> On Sunday 29 November 2009, Tatsuro MATSUOKA wrote:
> > Hello
> > 
> > Sorry for my duplicated post.
> > 
> > Does anyone explain the behavior below?
> > 
> > Regards
> > 
> > Tatsuro
> > 
> > 
> > --- Tatsuro MATSUOKA wrote:
> > 
> > > Sorry for my successive post.
> > > 
> > > I have looked at the config.log:
> > > 
> > > configure:8273: checking for LUA
> > > configure:8281: $PKG_CONFIG --exists --print-errors "lua"
> > > configure:8284: $? = 0
> > > configure:8299: $PKG_CONFIG --exists --print-errors "lua"
> > > configure:8302: $? = 0
> > > configure:8340: result: yes
> > > configure:8353: checking for library containing luaL_openlibs
> > > configure:8384: gcc-4 -o conftest.exe -O3 -fomit-frame-pointer   -I/usr/include  -L/usr/lib
> > > conftest.c
> > >  -llua -lm   >&5
> > > configure:8384: $? = 0
> > > configure:8401: result: none required
> > > configure:8411: checking lua.h usability
> > > configure:8411: gcc-4 -c -O3 -fomit-frame-pointer   -I/usr/include conftest.c >&5
> > > configure:8411: $? = 0
> > > configure:8411: result: yes
> > > configure:8411: checking lua.h presence
> > > configure:8411: gcc-4 -E   -I/usr/include conftest.c
> > > configure:8411: $? = 0
> > > configure:8411: result: yes
> > > configure:8411: checking for lua.h
> > > configure:8411: result: yes
> > > 
> > > *****************
> > > configure:8384: gcc-4 -o conftest.exe -O3 -fomit-frame-pointer   -I/usr/include  -L/usr/lib
> > > conftest.c
> > >  -llua -lm   >&5
> > > configure:8384: $? = 0
> > > configure:8401: result: none required
> > > ***************
> > >  $? = 0 but result: none required
> > > ????
> > > What is caused? I'm now in confusion.
> 
> I cannot help with cygwin.
> But the message above is not an error. I get the same report
> when building successfully under linux.  
> 
> configure:12416: checking for LUA
> configure:12483: result: yes
> configure:12442: $PKG_CONFIG --exists --print-errors "lua"
> configure:12445: $? = 0
> configure:12483: result: yes
> configure:12496: checking for library containing luaL_openlibs
> configure:12537: gcc -o conftest -g -O2   -I/usr/local/include   -L/usr/X11R6/lib  conftest.c
> -lm  -llua -lm   >&5
> configure:12544: $? = 0
> configure:12575: result: none required
> configure:12601: checking lua.h usability
> configure:12618: gcc -c -g -O2   -I/usr/local/include  conftest.c >&5
> configure:12625: $? = 0
> configure:12639: result: yes
> 
> I think this means that the test program created by the configure
> script compiles and links correctly without requiring any extra libraries.
> 
> I do notice a difference in the two configure logs, however.
> It seems from your log that the test for lua.h comes first, and then lua libraries second.
> My log shows first a test for the libraries and then a test for lua.h
> So the configure script may be different for some reason.
> 
> 
> 	Ethan
> 


--------------------------------------
Learn more about HIV/AIDS - Red Ribbon Campaign 2009
http://pr.mail.yahoo.co.jp/redribbon/

Hello

I have now testing to build gnuplot-4.4.0-rc1 on cygwin-1.7.
I found that 'make install-strip' fails: gnuplot.exe and gnuplot_x11.exe were not installed. Build
itself went well. So I manually install them and I could see,

              lua  Lua generic terminal driver
             tikz  TeX TikZ graphics macros via the lua script driver


This is perhaps due to Makefile try to build gnuplot-tikz.lua.exe on cygwin.
*************
make[3]: Entering directory
`/cygdrive/d/usr/Tatsu/cyghome-1.7/gnuplot-4.4/gnuplot-4.4.0-rc1-build/src'
make[3]: *** No rule to make target `gnuplot-tikz.lua.exe', needed by `all-am'.  Stop.
***************
I have gotten a big clue to kick out the problem. 

Perhaps something is wrong in src/Makefile.
I will look at it later.

Thanks for advises.

Regards

Tatsuro


--------------------------------------
Learn more about HIV/AIDS - Red Ribbon Campaign 2009
http://pr.mail.yahoo.co.jp/redribbon/