|
From: Mojca M. <moj...@gm...> - 2011-08-19 08:12:50
|
Dear Xenia, I'm forwarding your question to the gnuplot mailing list since they can probably help you better with this issue than people on the ConTeXt list. On Fri, Aug 19, 2011 at 09:47, Xenia wrote: >>> >>> I'm having some problems with gnuplot. >>> >>> I tried the minimal example from http://wiki.contextgarden.net/Gnuplot , >>> but I recieve just a .plt-file. >> >> 1.) What operating system are you using? > > debian-wheezy (testing) > >> 2.) Did you compile gnuplot from https://github.com/mojca/gnuplot or >> did you use the default gnuplot as shipped with your system? > > I tried following this instruction: > http://wiki.contextgarden.net/Gnuplot#Unix_or_Mac > > But then I got: > --------------------- > $ ./prepare > > ./prepare: 47: aclocal: not found > > Some part of the preparation process failed. > Please refer to INSTALL for details. > --------------------- > > And in "INSTALL" and "INSTALL.gnu" the first step is to do > $ ./configure > but I only have a configure.in and configure.vms -file. > I'm quite confused. > So I installed it from the debian-repositories (for sure without any > context-implementation), but you could just tell me, how I can make your > version work. :-) One option is probably also to patch gnuplot source package from Debian repositories, I don't know how to do that since I don't use Debian (but you only need to add context.trm to other terminals and add one #include "context.trm" line to src/term.h). The instructions in INSTALL are only valid for released versions when somebody else runs ./prepare instead of you before publishing the files. The ./prepare script creates ./configure. It would be really really helpful if configure script was included in source repository, but many argue that this would bring additional problems. (It could indeed happen that the file would get out-of-sync if somebody was modifying configuration and forgot to run ./prepare afterwards, but that would be spotted and resolved quickly. It would cause way less pain to "end users" trying to compile gnuplot from source.) You probably need to have autoconfigure installed or something like that. Others may know more precisely what is needed / what Debian package you need to install. Mojca |
|
From: Christoph B. <us...@be...> - 2011-08-19 08:59:36
|
On 19.08.2011 10:12, Mojca Miklavec wrote:
>
>> But then I got:
>> ---------------------
>> $ ./prepare
>>
>> ./prepare: 47: aclocal: not found
>>
>> Some part of the preparation process failed.
>> Please refer to INSTALL for details.
>> ---------------------
>>
>> And in "INSTALL" and "INSTALL.gnu" the first step is to do
>> $ ./configure
>> but I only have a configure.in and configure.vms -file.
>> I'm quite confused.
>> So I installed it from the debian-repositories (for sure without any
>> context-implementation), but you could just tell me, how I can make your
>> version work. :-)
>
> One option is probably also to patch gnuplot source package from
> Debian repositories, I don't know how to do that since I don't use
> Debian (but you only need to add context.trm to other terminals and
> add one #include "context.trm" line to src/term.h).
I guess this is the easiest option if you have no experience with
compilation of source code.
I hope, the following steps do what you need (I do not run wheezy). If
not, just ask again :-)
Get the source code of the debian package:
apt-get source gnuplot
Install the required dependencies for building gnuplot (this can be a lot!):
apt-get build-dep gnuplot
Change the code like Mojca wrote:
1. copy context.trm to gnuplot-4.4*/term/ (I do not know the exact
version number)
2. Add #include "context.trm" at the end of file term.h (right before
the last #endif statement)
cd gnuplot-4.4*
dpkg-buildpackage
Go and drink a coffee...
Install the .deb package manually:
cd ..
dpkg -i gnuplot*.deb
Mark those packages with 'hold' so that they are not overwritten on the
next upgrade (and this may happen soon on testing):
echo gnuplot hold | dpkg --set-selections
echo gnuplot-doc hold | dpkg --set-selections
echo gnuplot-nox hold | dpkg --set-selections
echo gnuplot-x11 hold | dpkg --set-selections
Christoph
|
|
From: Xenia <yo...@go...> - 2011-08-19 12:31:32
|
Am 19.08.2011 10:45, schrieb Christoph Bersch: > On 19.08.2011 10:12, Mojca Miklavec wrote: >> >>> But then I got: >>> --------------------- >>> $ ./prepare >>> >>> ./prepare: 47: aclocal: not found >>> >>> Some part of the preparation process failed. >>> Please refer to INSTALL for details. >>> --------------------- >>> >>> And in "INSTALL" and "INSTALL.gnu" the first step is to do >>> $ ./configure >>> but I only have a configure.in and configure.vms -file. >>> I'm quite confused. >>> So I installed it from the debian-repositories (for sure without any >>> context-implementation), but you could just tell me, how I can make your >>> version work. :-) >> >> One option is probably also to patch gnuplot source package from >> Debian repositories, I don't know how to do that since I don't use >> Debian (but you only need to add context.trm to other terminals and >> add one #include "context.trm" line to src/term.h). > > I guess this is the easiest option if you have no experience with > compilation of source code. > I hope, the following steps do what you need (I do not run wheezy). If > not, just ask again :-) > > Get the source code of the debian package: > apt-get source gnuplot > > Install the required dependencies for building gnuplot (this can be a lot!): > apt-get build-dep gnuplot > > Change the code like Mojca wrote: > 1. copy context.trm to gnuplot-4.4*/term/ (I do not know the exact > version number) > 2. Add #include "context.trm" at the end of file term.h (right before > the last #endif statement) > > cd gnuplot-4.4* > dpkg-buildpackage Something went wrong here. No .deb-file were created, an errormessage appeared (unfortenately I didn't save it). After I did some things (don't remember what I actually did), I tried it again and were requested to do a $ make distclean before. But again trying to build the package I got now: $ sudo dpkg-buildpackage dpkg-buildpackage: exportieren von CFLAGS aus dpkg-buildflags (Quelle: vendor): -g -O2 dpkg-buildpackage: exportieren von CPPFLAGS aus dpkg-buildflags (Quelle: vendor): dpkg-buildpackage: exportieren von CXXFLAGS aus dpkg-buildflags (Quelle: vendor): -g -O2 dpkg-buildpackage: exportieren von FFLAGS aus dpkg-buildflags (Quelle: vendor): -g -O2 dpkg-buildpackage: exportieren von LDFLAGS aus dpkg-buildflags (Quelle: vendor): dpkg-buildpackage: Quellpaket gnuplot dpkg-buildpackage: Quellversion 4.4.0-1.1 dpkg-buildpackage: Quellen geändert durch Agustin Martin Domingo <agm...@de...> dpkg-buildpackage: Host-Architektur amd64 dpkg-source --before-build gnuplot-4.4.0 debian/rules clean QUILT_PATCHES=debian/patches \ quilt --quiltrc /dev/null pop -a -R || test $? = 2 Patch debian-changes-4.4.0-1.1 kann nicht entfernt werden (Patch aktualisieren oder entfernen erzwingen mit -f) make: *** [unpatch] Fehler 1 dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules clean war 2 Means I have to remove or update the patch debian-changes… first. But I'm overextended. :-( > Go and drink a coffee... > > Install the .deb package manually: > > cd .. > dpkg -i gnuplot*.deb > > Mark those packages with 'hold' so that they are not overwritten on the > next upgrade (and this may happen soon on testing): > > echo gnuplot hold | dpkg --set-selections > echo gnuplot-doc hold | dpkg --set-selections > echo gnuplot-nox hold | dpkg --set-selections > echo gnuplot-x11 hold | dpkg --set-selections > > > Christoph > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > gnuplot-beta mailing list > gnu...@li... > https://lists.sourceforge.net/lists/listinfo/gnuplot-beta |
|
From: Christoph B. <us...@be...> - 2011-08-19 12:50:28
|
On 19.08.2011 14:32, Xenia wrote: > Am 19.08.2011 10:45, schrieb Christoph Bersch: >> dpkg-buildpackage > > Something went wrong here. No .deb-file were created, an errormessage > appeared (unfortenately I didn't save it). Well, that is essential. > After I did some things > (don't remember what I actually did), I tried it again and were > requested to do a > dpkg-buildpackage: Host-Architektur amd64 > dpkg-source --before-build gnuplot-4.4.0 > debian/rules clean > QUILT_PATCHES=debian/patches \ > quilt --quiltrc /dev/null pop -a -R || test $? = 2 > Patch debian-changes-4.4.0-1.1 kann nicht entfernt werden (Patch > aktualisieren oder entfernen erzwingen mit -f) > make: *** [unpatch] Fehler 1 > dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules clean war 2 > > Means I have to remove or update the patch debian-changes… first. I am not completely sure, but before the package is build again, dpkg-buildpackage seems to clean the source tree and unpatch the source. If guess your "fiddling" did something which now prevents the sources from being unpatched. The best thing would be to remove the sources, redo the steps (with the original sources, without Mojca's changes) and then give the error messages which you get when you call dpkg-buildpackage. Christoph |
|
From: Xenia <yo...@go...> - 2011-08-20 12:43:01
|
Am 19.08.2011 14:50, schrieb Christoph Bersch:
>>
>> Means I have to remove or update the patch debian-changes… first.
>
> I am not completely sure, but before the package is build again,
> dpkg-buildpackage seems to clean the source tree and unpatch the source.
> If guess your "fiddling" did something which now prevents the sources
> from being unpatched.
>
> The best thing would be to remove the sources, redo the steps (with the
> original sources, without Mojca's changes) and then give the error
> messages which you get when you call dpkg-buildpackage.
I deleted all patches, that seemed to disturb with
$ quilt delete …
and did
$ dpkg-buildpackage
again.
It resulted in the same errormessage, just some parts:
character constant [-Wmultichar]
../../../term/context.trm:2919:77133: warning: character constant too
long for its type [enabled by default]
../../../term/context.trm:2919:77160: warning: multi-character character
constant [-Wmultichar]
../../../term/context.trm:2919:77170: warning: character constant too
long for its type [enabled by default]
../../../term/context.trm:2919:77201: warning: multi-character ../../..
This repeats again and again; after that:
/term/context.trm:2919:17: error: stray ‘#’ in program
../../../term/context.trm:2919:17: error: stray ‘\’ in program
../../../term/context.trm:2919:17: error: stray ‘#’ in program
../../../term/context.trm:2919:79373: warning: multi-character character
constant [-Wmultichar]
../../../term/context.trm:2919:79383: warning: character constant too
long for its type [enabled by default]
[…]
../../../term/context.trm:2919:17: error: stray ‘\’ in program
[…]
In file included from ../../../src/term.h:458:0,
from ../../../src/term.c:1476:
../../../term/context.trm:3004:13: error: stray ‘#’ in program
../../../term/context.trm:3004:13: error: stray ‘#’ in program
../../../term/context.trm:3018:5: error: stray ‘#’ in program
[…]
../../../term/context.trm:3158:11: error: stray ‘\342’ in program
../../../term/context.trm:3158:11: error: stray ‘\206’ in program
../../../term/context.trm:3158:11: error: stray ‘\220’ in program
../../../term/context.trm:3162:11: error: stray ‘\342’ in program
../../../term/context.trm:3162:11: error: stray ‘\206’ in program
../../../term/context.trm:3162:11: error: stray ‘\222’ in program
../../../term/context.trm:3166:11: error: stray ‘\342’ in program
../../../term/context.trm:3166:11: error: stray ‘\206’ in program
../../../term/context.trm:3166:11: error: stray ‘\221’ in program
../../../term/context.trm:3170:11: error: stray ‘\342’ in program
../../../term/context.trm:3170:11: error: stray ‘\206’ in program
../../../term/context.trm:3170:11: error: stray ‘\223’ in program
../../../term/context.trm:3180:11: error: stray ‘\342’ in program
../../../term/context.trm:3180:11: error: stray ‘\206’ in program
../../../term/context.trm:3180:11: error: stray ‘\220’ in program
../../../term/context.trm:3184:11: error: stray ‘\342’ in program
../../../term/context.trm:3184:11: error: stray ‘\206’ in program
../../../term/context.trm:3184:11: error: stray ‘\222’ in program
../../../term/context.trm:3188:11: error: stray ‘\342’ in program
../../../term/context.trm:3188:11: error: stray ‘\206’ in program
../../../term/context.trm:3188:11: error: stray ‘\221’ in program
../../../term/context.trm:3192:11: error: stray ‘\342’ in program
../../../term/context.trm:3192:11: error: stray ‘\206’ in program
../../../term/context.trm:3192:11: error: stray ‘\223’ in program
../../../term/context.trm:3231:3: error: invalid preprocessing directive
#This
../../../term/context.trm:3232:1: error: stray ‘##’ in program
../../../term/context.trm:3233:1: error: stray ‘##’ in program
../../../term/context.trm:3233:1: error: stray ‘##’ in program
../../../term/context.trm:3233:1: error: stray ‘##’ in program
../../../term/context.trm:3250:10: error: invalid suffix "a" on integer
constant
../../../term/context.trm:3251:10: error: invalid suffix "b" on integer
constant
../../../term/context.trm:3257:11: error: invalid suffix "a" on integer
constant
../../../term/context.trm:3258:11: error: invalid suffix "b" on integer
constant
../../../term/context.trm:3274:5: warning: missing terminating '
character [enabled by default]
../../../term/context.trm:3274:1: error: missing terminating ' character
../../../term/context.trm:3285:1: error: stray ‘`’ in program
../../../term/context.trm:3285:1: error: stray ‘`’ in program
../../../term/context.trm:3285:1: error: stray ‘`’ in program
../../../term/context.trm:3288:20: warning: multi-character character
constant [-Wmultichar]
../../../term/context.trm:3291:1: error: stray ‘`’ in program
../../../term/context.trm:3291:1: error: stray ‘`’ in program
../../../term/context.trm:3291:1: error: stray ‘`’ in program
../../../term/context.trm:3307:1: error: stray ‘`’ in program
../../../term/context.trm:3307:1: error: stray ‘`’ in program
But not only errors about context.trm, also:
../../../src/term.c:2:14: warning: ‘RCSid’ defined but not used
[-Wunused-function]
../../../term/driver.h:45:13: warning: ‘do_point’ declared ‘static’ but
never defined [-Wunused-function]
../../../term/driver.h:46:13: warning: ‘line_and_point’ declared
‘static’ but never defined [-Wunused-function]
../../../term/driver.h:47:12: warning: ‘null_text_angle’ declared
‘static’ but never defined [-Wunused-function]
../../../term/driver.h:48:12: warning: ‘null_justify_text’ declared
‘static’ but never defined [-Wunused-function]
../../../term/driver.h:49:12: warning: ‘null_scale’ declared ‘static’
but never defined [-Wunused-function]
../../../term/driver.h:50:13: warning: ‘options_null’ declared ‘static’
but never defined [-Wunused-function]
../../../term/driver.h:51:13: warning: ‘UNKNOWN_null’ declared ‘static’
but never defined [-Wunused-function]
make[2]: *** [term.o] Fehler 1
make[2]: Leaving directory `/home/user/gnuplot-4.4.0/debian/build-nox/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/user/gnuplot-4.4.0/debian/build-nox/src'
make: *** [build-nox-stamp] Fehler 2
dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2
What to do?
Thanks a lot for you patience and help.
Xenia
|
|
From: Christoph B. <us...@be...> - 2011-08-20 13:22:06
|
On 20.08.2011 14:43 Xenia wrote: > Am 19.08.2011 14:50, schrieb Christoph Bersch: >>> >>> Means I have to remove or update the patch debian-changes… first. >> >> I am not completely sure, but before the package is build again, >> dpkg-buildpackage seems to clean the source tree and unpatch the source. >> If guess your "fiddling" did something which now prevents the sources >> from being unpatched. >> >> The best thing would be to remove the sources, redo the steps (with the >> original sources, without Mojca's changes) and then give the error >> messages which you get when you call dpkg-buildpackage. > > I deleted all patches, that seemed to disturb with You should not do that because you remove also the debian-specific patches which also change the paths where everything is installed! The problem is (I found it out now), that when you call dpkg-buildpackage for the first time, the build system creates a patch with the changes that you made (with the context terminal). If after the first build you change something, running dpkg-buildpackage again does not work because the sources cannot be unpatched. > $ quilt delete … > and did > $ dpkg-buildpackage > again. > It resulted in the same errormessage, just some parts: > > character constant [-Wmultichar] > ../../../term/context.trm:2919:77133: warning: character constant too > long for its type [enabled by default] [...] > ../../../term/context.trm:3307:1: error: stray ‘`’ in program I guess, you downloaded the wrong context.trm, maybe the HTML-view of the git Repository. The context.trm which I got from <https://raw.github.com/mojca/gnuplot/master/term/context.trm> has only 2395 lines! Further, if you want to compile it with 4.4 you must remove the string "| TERM_FONTSCALE | TERM_IS_LATEX" in line 2222, which is not supported in 4.4.0. So completely remove the gnuplot-4* directory, and do all the steps again from scratch (apt-get source also does not download the source again, but just unpacks them). Christoph |
|
From: Xenia <yo...@go...> - 2011-08-20 14:04:30
|
Am 20.08.2011 15:21, schrieb Christoph Bersch: > On 20.08.2011 14:43 Xenia wrote: >> Am 19.08.2011 14:50, schrieb Christoph Bersch: >>>> >>>> Means I have to remove or update the patch debian-changes… first. >>> >>> I am not completely sure, but before the package is build again, >>> dpkg-buildpackage seems to clean the source tree and unpatch the source. >>> If guess your "fiddling" did something which now prevents the sources >>> from being unpatched. >>> >>> The best thing would be to remove the sources, redo the steps (with the >>> original sources, without Mojca's changes) and then give the error >>> messages which you get when you call dpkg-buildpackage. >> >> I deleted all patches, that seemed to disturb with > > You should not do that because you remove also the debian-specific > patches which also change the paths where everything is installed! > > The problem is (I found it out now), that when you call > dpkg-buildpackage for the first time, the build system creates a patch > with the changes that you made (with the context terminal). If after the > first build you change something, running dpkg-buildpackage again does > not work because the sources cannot be unpatched. > >> $ quilt delete … >> and did >> $ dpkg-buildpackage >> again. >> It resulted in the same errormessage, just some parts: >> >> character constant [-Wmultichar] >> ../../../term/context.trm:2919:77133: warning: character constant too >> long for its type [enabled by default] > [...] >> ../../../term/context.trm:3307:1: error: stray ‘`’ in program > > I guess, you downloaded the wrong context.trm, maybe the HTML-view of > the git Repository. The context.trm which I got from > <https://raw.github.com/mojca/gnuplot/master/term/context.trm> has only > 2395 lines! > > Further, if you want to compile it with 4.4 you must remove the string > "| TERM_FONTSCALE | TERM_IS_LATEX" in line 2222, which is not supported > in 4.4.0. Is this documented somewhere (in case I want to update someday and there are similar behaviours)? > So completely remove the gnuplot-4* directory, and do all the steps > again from scratch (apt-get source also does not download the source > again, but just unpacks them). It now really works. Great. Thank you very much. :-) Xenia |
|
From: Christoph B. <us...@be...> - 2011-08-21 13:54:01
|
On 20.08.2011 16:05 Xenia wrote: > Am 20.08.2011 15:21, schrieb Christoph Bersch: >> >> Further, if you want to compile it with 4.4 you must remove the string >> "| TERM_FONTSCALE | TERM_IS_LATEX" in line 2222, which is not supported >> in 4.4.0. > > Is this documented somewhere (in case I want to update someday and there > are similar behaviours)? No, I tried to compile the context.trm myself with the 4.4 version and got an error about unknown TERM_FONTSCALE and found that this is only defined in the cvs version. >> So completely remove the gnuplot-4* directory, and do all the steps >> again from scratch (apt-get source also does not download the source >> again, but just unpacks them). > > It now really works. Great. Great, good to hear :-) Christoph |