Menu
▾
▴
gnuplot-beta
|
From: Tatsuro M. <tma...@ya...> - 2009-11-30 10:57:47
|
Hello In the src/Makefile.in after ./prepare, I found. @BUILD_LUA_TRUE@am__EXEEXT_2 = 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. BTW, after removing $(EXEEXT) form @BUILD_LUA_TRUE@am__EXEEXT_2 = 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 -------------------------------------- Learn more about HIV/AIDS - Red Ribbon Campaign 2009 http://pr.mail.yahoo.co.jp/redribbon/ |
|
From: Ethan M. <merritt@u.washington.edu> - 2009-11-30 20:21:09
|
On Monday 30 November 2009 02:57:27 Tatsuro MATSUOKA wrote: > Hello > > In the src/Makefile.in after ./prepare, I found. > > @BUILD_LUA_TRUE@am__EXEEXT_2 = 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@am__EXEEXT_2 = 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 |
|
From: Tatsuro M. <tma...@ya...> - 2009-12-01 04:42:52
|
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/ |
|
From: Tatsuro M. <tma...@ya...> - 2009-12-01 04:45:43
|
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/ |
|
From: Hans-Bernhard B. <HBB...@t-...> - 2009-11-30 22:42:25
|
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. |
|
From: Tatsuro M. <tma...@ya...> - 2009-12-01 01:14:10
|
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 > gnu...@li... > https://lists.sourceforge.net/lists/listinfo/gnuplot-beta > -------------------------------------- Learn more about HIV/AIDS - Red Ribbon Campaign 2009 http://pr.mail.yahoo.co.jp/redribbon/ |
|
From: Ethan M. <merritt@u.washington.edu> - 2009-12-01 01:19:38
|
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 |
