|
From: Achim G. <Str...@ne...> - 2017-10-15 15:40:32
|
The configury supposedly tries to find TEXDIR via kpsexpand, but that
code never gets run if $prefix is set. I think the code should rather do
this:
--8<---------------cut here---------------start------------->8---
--- origsrc/gnuplot-branch-5-2-stable/configure.ac 2017-10-14 02:00:11.000000000 +0200
+++ src/gnuplot-branch-5-2-stable/configure.ac 2017-10-15 17:31:46.192683400 +0200
@@ -146,11 +146,11 @@ if test "$with_latex" = yes; then
[texdir is not given and there is no kpsexpand, please tell where to install])
dnl texdir has priority
if test "$TEXDIR" = "no"; then
- if test "x$prefix" != "xNONE"; then
- TEXDIR=${prefix}/share/texmf
- else
- TEXDIR=`$KPSEXPAND '$TEXMFLOCAL'`
- if test "x$TEXDIR" = "x" -o "$TEXDIR" = "\$TEXMFLOCAL"; then
+ TEXDIR=`$KPSEXPAND '$TEXMFLOCAL'`
+ if test "x$TEXDIR" = "x" -o "$TEXDIR" = "\$TEXMFLOCAL"; then
+ if test "x$prefix" != "xNONE"; then
+ TEXDIR=${prefix}/share/texmf
+ else
TEXDIR=${ac_default_prefix}/share/texmf
fi
fi
--8<---------------cut here---------------end--------------->8---
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
|
|
From: Ethan A M. <sf...@us...> - 2017-10-17 00:36:15
|
On Sunday, 15 October, 2017 17:40:03 Achim Gratz wrote:
>
> The configury supposedly tries to find TEXDIR via kpsexpand, but that
> code never gets run if $prefix is set.
I really don't know if this is correct or not.
In my experience there are so many places that the TeX stuff
might go, your only hope is to manually specify where it is
on the current system. It doesn't help any that according to the
man page
"the syntax for kpsexpand is incompatible with teTeX´s as of version 0.4"
I read the existing ./configure logic to be that anything kpsexpand
returns is where things would be by default, but if you are specifying
a $prefix then you are overriding the default.
Does it ever make sense to mix the two?
What do other people think?
Ethan
> I think the code should rather do this:
>
> --8<---------------cut here---------------start------------->8---
> --- origsrc/gnuplot-branch-5-2-stable/configure.ac 2017-10-14 02:00:11.000000000 +0200
> +++ src/gnuplot-branch-5-2-stable/configure.ac 2017-10-15 17:31:46.192683400 +0200
> @@ -146,11 +146,11 @@ if test "$with_latex" = yes; then
> [texdir is not given and there is no kpsexpand, please tell where to install])
> dnl texdir has priority
> if test "$TEXDIR" = "no"; then
> - if test "x$prefix" != "xNONE"; then
> - TEXDIR=${prefix}/share/texmf
> - else
> - TEXDIR=`$KPSEXPAND '$TEXMFLOCAL'`
> - if test "x$TEXDIR" = "x" -o "$TEXDIR" = "\$TEXMFLOCAL"; then
> + TEXDIR=`$KPSEXPAND '$TEXMFLOCAL'`
> + if test "x$TEXDIR" = "x" -o "$TEXDIR" = "\$TEXMFLOCAL"; then
> + if test "x$prefix" != "xNONE"; then
> + TEXDIR=${prefix}/share/texmf
> + else
> TEXDIR=${ac_default_prefix}/share/texmf
> fi
> fi
> --8<---------------cut here---------------end--------------->8---
>
>
> Regards,
> Achim.
>
|
|
From: Daniel J S. <dan...@ie...> - 2017-10-17 01:29:52
|
On 10/16/2017 07:35 PM, Ethan A Merritt via gnuplot-beta wrote:
> On Sunday, 15 October, 2017 17:40:03 Achim Gratz wrote:
>
> >
>
> > The configury supposedly tries to find TEXDIR via kpsexpand, but that
>
> > code never gets run if $prefix is set.
>
> I really don't know if this is correct or not.
>
> In my experience there are so many places that the TeX stuff
>
> might go, your only hope is to manually specify where it is
>
> on the current system. It doesn't help any that according to the
>
> man page
>
> "the syntax for kpsexpand is incompatible with teTeX´s as of version 0.4"
>
> I read the existing ./configure logic to be that anything kpsexpand
>
> returns is where things would be by default, but if you are specifying
>
> a $prefix then you are overriding the default.
>
> Does it ever make sense to mix the two?
>
> What do other people think?
Well, this
AC_ARG_WITH(texdir,dnl
[--with-texdir=DIR where to install latex style files
(default by kpsexpand in subdir PACKAGE)],
TEXDIR="$withval",
TEXDIR="no")
means a person can't choose a directory name "no".
The goal is to find a location for gnuplot's few supplemental tex/latex
files? I presume we really don't want those to go to kpsexpand's local
tex; that's the system's copy of tex source. Most typically we want the
extra TeX files to go somewhere in the directory tree where gnuplot is
installed. Is that correct?
So, the logic of the current configure is (if no TEXDIR is specified) to
choose the location where gnuplot is installed as the base directory for
where TeX files will be placed. If there is no such prefix, then it
looks to the default kpsexpand location. I presume that when the TeX
files are installed at the location of the gnuplot executable that the
TeX path is somehow added to the TeX system paths?
From Achim's patch of the first email:
+ TEXDIR=`$KPSEXPAND '$TEXMFLOCAL'`
+ if test "x$TEXDIR" = "x" -o "$TEXDIR" = "\$TEXMFLOCAL"; then
Aren't these two lines doing the same thing, in most cases? Anyway, the
patch seems to make kpsexpand's location for system TeX files the higher
priority location.
Dan
|
|
From: Achim G. <Str...@ne...> - 2017-10-18 08:17:49
|
Ethan A Merritt via gnuplot-beta writes: > I really don't know if this is correct or not. Me neither, but at least it provides the result I need for building gnuplot on Cygwin (with cygport) without explicit specififcation of TEXDIR. Cygport does set $prefix on invocation of the configury, so I did get an unexpected (and non-working) TEXDIR location. This is ion contrast to the openSUSE Linux distributions I consulted the build logs of their package for and the reason for the unexpected behaviour was that their build system apparently does not explicitly set $prefix (but must have the default prefix pointing to the system and not the local installation directories). > In my experience there are so many places that the TeX stuff might go, > your only hope is to manually specify where it is on the current > system. It doesn't help any that according to the man page "the > syntax for kpsexpand is incompatible with teTeX´s as of version 0.4" Ehm… teTex is unmaintained for over ten years now and was always suggested to be replaced by TeXLive, which is what all major distros and of course also Cygwin are using. > I read the existing ./configure logic to be that anything kpsexpand > returns is where things would be by default, but if you are specifying > a $prefix then you are overriding the default. > Does it ever make sense to mix the two? The generic $prefix should just decide which of potentially several install locations is chosen (eg. /usr, /usr/local, /opt, …). But in this test as originally written, specifying a $prefix (even if it's just repeating the default location) makes configure fall back to the "I don't know anything" branch that puts those files under an application specific directory. This is at least surprising, if not plain wrong. I have no idea if there's a better way to ask autotools about the proper location (I didn't find any pkg-config stuff for TeXLive), but it seems that this should be a problem that has already been solved elsewhere. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds |
|
From: Daniel J S. <dan...@ie...> - 2017-10-17 01:42:41
|
On 10/16/2017 08:29 PM, Daniel J Sebald wrote:
> On 10/16/2017 07:35 PM, Ethan A Merritt via gnuplot-beta wrote:
> > On Sunday, 15 October, 2017 17:40:03 Achim Gratz wrote:
> >
> > >
> >
> > > The configury supposedly tries to find TEXDIR via kpsexpand, but that
> >
> > > code never gets run if $prefix is set.
> >
> > I really don't know if this is correct or not.
> >
> > In my experience there are so many places that the TeX stuff
> >
> > might go, your only hope is to manually specify where it is
> >
> > on the current system. It doesn't help any that according to the
> >
> > man page
> >
> > "the syntax for kpsexpand is incompatible with teTeX´s as of version
> 0.4"
> >
> > I read the existing ./configure logic to be that anything kpsexpand
> >
> > returns is where things would be by default, but if you are specifying
> >
> > a $prefix then you are overriding the default.
> >
> > Does it ever make sense to mix the two?
> >
> > What do other people think?
>
> Well, this
>
> AC_ARG_WITH(texdir,dnl
> [--with-texdir=DIR where to install latex style files
> (default by kpsexpand in subdir PACKAGE)],
> TEXDIR="$withval",
> TEXDIR="no")
>
> means a person can't choose a directory name "no".
>
> The goal is to find a location for gnuplot's few supplemental tex/latex
> files? I presume we really don't want those to go to kpsexpand's local
> tex; that's the system's copy of tex source. Most typically we want the
> extra TeX files to go somewhere in the directory tree where gnuplot is
> installed. Is that correct?
>
> So, the logic of the current configure is (if no TEXDIR is specified) to
> choose the location where gnuplot is installed as the base directory for
> where TeX files will be placed. If there is no such prefix, then it
> looks to the default kpsexpand location. I presume that when the TeX
> files are installed at the location of the gnuplot executable that the
> TeX path is somehow added to the TeX system paths?
Oh, wait, I don't think I was understanding that correctly. kpsexpand's
'$TEXMFLOCAL' is a location for "non-system" TeX files (that will be
recognized in TeX/LaTeX's path?). So, that is typically where we want
files to go, regardless of whether one indicates a gnuplot installation
prefix or not. Is that right? We really want to use $prefix as a last
resort then, correct? In that case, I would go with what Achim is arguing.
+ TEXDIR=`$KPSEXPAND '$TEXMFLOCAL'`
[Do we know that kpsexpand is present once reaching this point?]
+ if test "x$TEXDIR" = "x" -o "$TEXDIR" = "\$TEXMFLOCAL"; then
[If kpsexpand fails to find a TEXMFLOCAL, how do we know that
TEXMFLOCAL is going to be present in our environment? Just hoping by
chance that it is? If we didn't have kpsexpand, I could see attempting
this last-ditch effort.]
+ if test "x$prefix" != "xNONE"; then
+ TEXDIR=${prefix}/share/texmf
+ else
TEXDIR=${ac_default_prefix}/share/texmf
fi
Dan
|
|
From: sfeam <sf...@us...> - 2017-10-17 03:58:13
|
Is this issue the same as Bug #1119? https://sourceforge.net/p/gnuplot/bugs/1119/ Ethan On Monday, 16 October 2017 20:42:32 Daniel J Sebald wrote: > On 10/16/2017 08:29 PM, Daniel J Sebald wrote: > > On 10/16/2017 07:35 PM, Ethan A Merritt via gnuplot-beta wrote: > > > On Sunday, 15 October, 2017 17:40:03 Achim Gratz wrote: > > > > > > > > > > > > > > The configury supposedly tries to find TEXDIR via kpsexpand, but that > > > > > > > code never gets run if $prefix is set. > > > > > > I really don't know if this is correct or not. > > > > > > In my experience there are so many places that the TeX stuff > > > > > > might go, your only hope is to manually specify where it is > > > > > > on the current system. It doesn't help any that according to the > > > > > > man page > > > > > > "the syntax for kpsexpand is incompatible with teTeX´s as of version > > 0.4" > > > > > > I read the existing ./configure logic to be that anything kpsexpand > > > > > > returns is where things would be by default, but if you are specifying > > > > > > a $prefix then you are overriding the default. > > > > > > Does it ever make sense to mix the two? > > > > > > What do other people think? > > > > Well, this > > > > AC_ARG_WITH(texdir,dnl > > [--with-texdir=DIR where to install latex style files > > (default by kpsexpand in subdir PACKAGE)], > > TEXDIR="$withval", > > TEXDIR="no") > > > > means a person can't choose a directory name "no". > > > > The goal is to find a location for gnuplot's few supplemental tex/latex > > files? I presume we really don't want those to go to kpsexpand's local > > tex; that's the system's copy of tex source. Most typically we want the > > extra TeX files to go somewhere in the directory tree where gnuplot is > > installed. Is that correct? > > > > So, the logic of the current configure is (if no TEXDIR is specified) to > > choose the location where gnuplot is installed as the base directory for > > where TeX files will be placed. If there is no such prefix, then it > > looks to the default kpsexpand location. I presume that when the TeX > > files are installed at the location of the gnuplot executable that the > > TeX path is somehow added to the TeX system paths? > > Oh, wait, I don't think I was understanding that correctly. kpsexpand's > '$TEXMFLOCAL' is a location for "non-system" TeX files (that will be > recognized in TeX/LaTeX's path?). So, that is typically where we want > files to go, regardless of whether one indicates a gnuplot installation > prefix or not. Is that right? We really want to use $prefix as a last > resort then, correct? In that case, I would go with what Achim is arguing. > > + TEXDIR=`$KPSEXPAND '$TEXMFLOCAL'` > > [Do we know that kpsexpand is present once reaching this point?] > > + if test "x$TEXDIR" = "x" -o "$TEXDIR" = "\$TEXMFLOCAL"; then > > [If kpsexpand fails to find a TEXMFLOCAL, how do we know that > TEXMFLOCAL is going to be present in our environment? Just hoping by > chance that it is? If we didn't have kpsexpand, I could see attempting > this last-ditch effort.] > > + if test "x$prefix" != "xNONE"; then > + TEXDIR=${prefix}/share/texmf > + else > TEXDIR=${ac_default_prefix}/share/texmf > fi > > Dan > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > gnuplot-beta mailing list > gnu...@li... > Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta |
|
From: Daniel J S. <dan...@ie...> - 2017-10-17 04:21:09
|
On 10/16/2017 10:57 PM, sfeam wrote: > Is this issue the same as Bug #1119? > > https://sourceforge.net/p/gnuplot/bugs/1119/ > > Ethan It certainly looks like the same issue. I don't know how Macports works or why it is unable to remove the files (presuming Macports has adequate privilege). Also, I can understand the various directories for different types of files, but whether those subdirectories are meant to be a subdirectory of TEXDIR or somewhere else I'm not sure. Dan > On Monday, 16 October 2017 20:42:32 Daniel J Sebald wrote: >> On 10/16/2017 08:29 PM, Daniel J Sebald wrote: >>> On 10/16/2017 07:35 PM, Ethan A Merritt via gnuplot-beta wrote: >>> > On Sunday, 15 October, 2017 17:40:03 Achim Gratz wrote: >>> > >>> > > >>> > >>> > > The configury supposedly tries to find TEXDIR via kpsexpand, but that >>> > >>> > > code never gets run if $prefix is set. >>> > >>> > I really don't know if this is correct or not. >>> > >>> > In my experience there are so many places that the TeX stuff >>> > >>> > might go, your only hope is to manually specify where it is >>> > >>> > on the current system. It doesn't help any that according to the >>> > >>> > man page >>> > >>> > "the syntax for kpsexpand is incompatible with teTeX´s as of version >>> 0.4" >>> > >>> > I read the existing ./configure logic to be that anything kpsexpand >>> > >>> > returns is where things would be by default, but if you are specifying >>> > >>> > a $prefix then you are overriding the default. >>> > >>> > Does it ever make sense to mix the two? >>> > >>> > What do other people think? >>> >>> Well, this >>> >>> AC_ARG_WITH(texdir,dnl >>> [--with-texdir=DIR where to install latex style files >>> (default by kpsexpand in subdir PACKAGE)], >>> TEXDIR="$withval", >>> TEXDIR="no") >>> >>> means a person can't choose a directory name "no". >>> >>> The goal is to find a location for gnuplot's few supplemental tex/latex >>> files? I presume we really don't want those to go to kpsexpand's local >>> tex; that's the system's copy of tex source. Most typically we want the >>> extra TeX files to go somewhere in the directory tree where gnuplot is >>> installed. Is that correct? >>> >>> So, the logic of the current configure is (if no TEXDIR is specified) to >>> choose the location where gnuplot is installed as the base directory for >>> where TeX files will be placed. If there is no such prefix, then it >>> looks to the default kpsexpand location. I presume that when the TeX >>> files are installed at the location of the gnuplot executable that the >>> TeX path is somehow added to the TeX system paths? >> >> Oh, wait, I don't think I was understanding that correctly. kpsexpand's >> '$TEXMFLOCAL' is a location for "non-system" TeX files (that will be >> recognized in TeX/LaTeX's path?). So, that is typically where we want >> files to go, regardless of whether one indicates a gnuplot installation >> prefix or not. Is that right? We really want to use $prefix as a last >> resort then, correct? In that case, I would go with what Achim is arguing. >> >> + TEXDIR=`$KPSEXPAND '$TEXMFLOCAL'` >> >> [Do we know that kpsexpand is present once reaching this point?] >> >> + if test "x$TEXDIR" = "x" -o "$TEXDIR" = "\$TEXMFLOCAL"; then >> >> [If kpsexpand fails to find a TEXMFLOCAL, how do we know that >> TEXMFLOCAL is going to be present in our environment? Just hoping by >> chance that it is? If we didn't have kpsexpand, I could see attempting >> this last-ditch effort.] >> >> + if test "x$prefix" != "xNONE"; then >> + TEXDIR=${prefix}/share/texmf >> + else >> TEXDIR=${ac_default_prefix}/share/texmf >> fi >> >> Dan >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> gnuplot-beta mailing list >> gnu...@li... >> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta |
|
From: Mojca M. <moj...@gm...> - 2017-10-17 05:34:30
|
16. okt. 2017 8:58 PM je oseba "sfeam via gnuplot-beta" napisala: Is this issue the same as Bug #1119? https://sourceforge.net/p/gnuplot/bugs/1119/ It's not. The main problem there is that DESTDIR is not respected and make clean would not remove files either. Mojca |
|
From: Daniel J S. <dan...@ie...> - 2017-10-17 07:54:40
|
On 10/17/2017 12:34 AM, Mojca Miklavec wrote: > > > 16. okt. 2017 8:58 PM je oseba "sfeam via gnuplot-beta" napisala: > > Is this issue the same as Bug #1119? > > https://sourceforge.net/p/gnuplot/bugs/1119/ > <https://sourceforge.net/p/gnuplot/bugs/1119/> > > > It's not. The main problem there is that DESTDIR is not respected and > make clean would not remove files either. That's "make uninstall", as opposed to "clean", correct? Let's continue at the bug-report site. Dan |