|
From: Mojca M. <moj...@gm...> - 2011-02-17 09:59:03
|
On Thu, Feb 17, 2011 at 10:02, Andrea D'Amore wrote: > On Mon, Feb 14, 2011 at 10:31 AM, Mojca Miklavec wrote: >> Dear list, >> if I remove MacPorts from PATH (I had to do it since I have serious >> problems with AquaTerm), building fails with: > > Out of curiosity why did you remove mp from PATH? A few times I have tried to build a standalone gnuplot (independent of macports), but this time I was doing experiments with AquaTerm. AquaTerm doesn't provide 64-bit binaries and was just experimenting with that. If I build gnuplot with MacPorts then AquaTerm works (however the latest version of gnuplot complains that aquaterm doesn't support transparency and it complains when I build it). But when I use macports, I cannot test if my own build of AquaTerm works (apparently it doesn't, but that's an independent issue). > You can still use > x11 terminal even with MacPorts' build of gnuplot. I'm not interested in x11 (except that I'm lucky to have a working backup terminal when aquaterm fails), but in particular I'm not interested in MacPorts' gnuplot since it doesn't satisfy my needs. > Btw I've tried to use macports to build gnuplot with a default x11 > terminal and I wasn't able to do that, no matter what the env is, > configure manage to set aqua as default terminal. I ended using "set > terminal x11" into ~/.gnuplot . If I uninstall system-wide AquaTerm and only keep the one shipped with MacPorts, gnuplot won't even compile with AquaTerm support, so I always get x11 (for some reason I like AquaTerm more despite many of its drawbacks). Mojca |
|
From: Andrea D'A. <and...@ma...> - 2011-02-17 10:14:48
|
On Thu, Feb 17, 2011 at 10:58 AM, Mojca Miklavec <moj...@gm...> wrote: >> Btw I've tried to use macports to build gnuplot with a default x11 >> terminal and I wasn't able to do that, no matter what the env is, >> configure manage to set aqua as default terminal. I ended using "set >> terminal x11" into ~/.gnuplot . > If I uninstall system-wide AquaTerm and only keep the one shipped with > MacPorts, gnuplot won't even compile with AquaTerm support, so I > always get x11 And this is just ironic. -- Andrea |
|
From: Clark G. <cga...@vt...> - 2011-03-01 23:21:23
|
iirc, aquaterm has no 64-bit support, in that it does not build 64bit if you try. x11 does and gnuplot does. hence if you try to force aquaterm build, you get unfindable objects. discard aquaterm or revitalize it; it is a lamentable loss, but it is dead, imho. --ckg On Thu, 17 Feb 2011 10:58 +0100, "Mojca Miklavec" <moj...@gm...> wrote: > On Thu, Feb 17, 2011 at 10:02, Andrea D'Amore wrote: > > On Mon, Feb 14, 2011 at 10:31 AM, Mojca Miklavec wrote: > >> Dear list, > >> if I remove MacPorts from PATH (I had to do it since I have serious > >> problems with AquaTerm), building fails with: > > > > Out of curiosity why did you remove mp from PATH? > > A few times I have tried to build a standalone gnuplot (independent of > macports), but this time I was doing experiments with AquaTerm. > AquaTerm doesn't provide 64-bit binaries and was just experimenting > with that. If I build gnuplot with MacPorts then AquaTerm works > (however the latest version of gnuplot complains that aquaterm doesn't > support transparency and it complains when I build it). > > But when I use macports, I cannot test if my own build of AquaTerm > works (apparently it doesn't, but that's an independent issue). > > > You can still use > > x11 terminal even with MacPorts' build of gnuplot. > > I'm not interested in x11 (except that I'm lucky to have a working > backup terminal when aquaterm fails), but in particular I'm not > interested in MacPorts' gnuplot since it doesn't satisfy my needs. > > > Btw I've tried to use macports to build gnuplot with a default x11 > > terminal and I wasn't able to do that, no matter what the env is, > > configure manage to set aqua as default terminal. I ended using "set > > terminal x11" into ~/.gnuplot . > > If I uninstall system-wide AquaTerm and only keep the one shipped with > MacPorts, gnuplot won't even compile with AquaTerm support, so I > always get x11 (for some reason I like AquaTerm more despite many of > its drawbacks). > > Mojca > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > gnuplot-beta mailing list > gnu...@li... > https://lists.sourceforge.net/lists/listinfo/gnuplot-beta > -- Clark Gaylord Chief Information Officer Virginia Tech Transportation Institute cga...@vt... +1 (540) 231-2347 |
|
From: Mojca M. <moj...@gm...> - 2011-03-02 07:35:35
|
On Wed, Mar 2, 2011 at 00:01, Clark Gaylord wrote: > iirc, aquaterm has no 64-bit support, in that it does not build 64bit if > you try. x11 does and gnuplot does. hence if you try to force aquaterm > build, you get unfindable objects. discard aquaterm or revitalize it; it > is a lamentable loss, but it is dead, imho. I tried to patch AquaTerm, so it now builds as 64-bit, it does link to gnuplot, but for a misterious reason it hans forever when I try to plot something and I need to figure out how to figure out what goes wrong. (Somebody else contributed a set of patches that change all "int"s into "int_32" etc. I will try to merge those patches as well.) I need to explore why that happens since the version from macports works just fine. There are many aspects of AquaTerm that I still try to understand. I'm willing to work on fixing AquaTerm, but I'm still learning. AquaTerm may not be in the best shape, I know, but as long as it works (if I can figure out how to build it for 64-bit so that it won't hand), there is no reason to discard it yet. Mojca |