On Fri, May 2, 2014 at 2:38 PM, leif wrote:
> William Stein wrote:
>>
>> I just spent a while trying to figure out how to get R png graphics to
>> work again in Sage-6.2rc0 on Ubuntu 14.04. Note that graphics worked
>> fine with Sage-6.2beta1 on Ubuntu 12.04.Karl Dieter's many random
>> posts
William Stein wrote:
I just spent a while trying to figure out how to get R png graphics to
work again in Sage-6.2rc0 on Ubuntu 14.04. Note that graphics worked
fine with Sage-6.2beta1 on Ubuntu 12.04.Karl Dieter's many random
posts around the web asking about this problem were helpful, thou
On Fri, May 02, 2014 at 09:48:50AM +, Francois Bissey wrote:
> I know what you want to say Felix but once the pre-requisite are in place
> we are more less performing all the install from a "sage shell" in which
> sage-env is used to set the environment.
a sage shell is not necessary to run th
I know what you want to say Felix but once the pre-requisite are in place
we are more less performing all the install from a "sage shell" in which
sage-env is used to set the environment.
When spkg-install is at work, sage-env is read. At least that's how I understand
it works.
Francois
On 2/05/2
On Fri, May 02, 2014 at 09:12:34AM +1200, François Bissey wrote:
> > We could put it into sage-env as well, but regarding how often that's
> > called...
>
> I was actually thinking of feeding it to sage-env :)
sage-env is a part of sage ("the library"). the environment for
pkgconfig (and probably
On Fri, 02 May 2014 01:34:42 leif wrote:
> François Bissey wrote:
> > On Thu, 01 May 2014 15:05:03 Volker Braun wrote:
> >> On Thursday, May 1, 2014 9:58:47 PM UTC+1, leif wrote:
> pkg-config --variable pc_path pkg-config
> >>>
> >>> That doesn't always work. (See my other post on how to get
François Bissey wrote:
On Thu, 01 May 2014 15:05:03 Volker Braun wrote:
On Thursday, May 1, 2014 9:58:47 PM UTC+1, leif wrote:
pkg-config --variable pc_path pkg-config
That doesn't always work. (See my other post on how to get it.)
Where does it not work?
My SLES11SP1 system on power7 rep
On Fri, 02 May 2014 11:04:35 François Bissey wrote:
> On Thu, 01 May 2014 15:05:03 Volker Braun wrote:
> > On Thursday, May 1, 2014 9:58:47 PM UTC+1, leif wrote:
> > > > pkg-config --variable pc_path pkg-config
> > >
> > > That doesn't always work. (See my other post on how to get it.)
> >
> > W
On Thu, 01 May 2014 15:05:03 Volker Braun wrote:
> On Thursday, May 1, 2014 9:58:47 PM UTC+1, leif wrote:
> > > pkg-config --variable pc_path pkg-config
> >
> > That doesn't always work. (See my other post on how to get it.)
>
> Where does it not work?
My SLES11SP1 system on power7 reports:
frb1
On Thu, May 01, 2014 at 10:58:47PM +0200, leif wrote:
> Felix Salfelder wrote:
> >pkg-config --variable pc_path pkg-config
>
> That doesn't always work. (See my other post on how to get it.)
if so (when?), how about fallback to something more complex *in case it
does not*?
reportedly, --debug d
On Thursday, May 1, 2014 9:25:52 PM UTC+1, leif wrote:
>
> $ pkg-config --debug 2>&1 | awk '/^Scanning /{print
Pkgconf (the implementation that we are actually using in Sage) does not
have a --debug switch.
--
You received this message because you are subscribed to the Google Groups
"sage-
On Thursday, May 1, 2014 9:58:47 PM UTC+1, leif wrote:
>
> > pkg-config --variable pc_path pkg-config
> That doesn't always work. (See my other post on how to get it.)
>
Where does it not work?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
T
It does have a configure option:
$ ./configure --help
`configure' configures pkgconf 0.9.4 to adapt to many kinds of systems.
[...]
--with-pkg-config-dir specify the place where pc files will be found
On Thursday, May 1, 2014 10:45:12 PM UTC+1, leif wrote:
>
> Well, we could just patch our p
François Bissey wrote:
On Thu, 01 May 2014 23:06:53 leif wrote:
François Bissey wrote:
On Thu, 01 May 2014 22:58:47 leif wrote:
Felix Salfelder wrote:
pkg-config --variable pc_path pkg-config
That doesn't always work. (See my other post on how to get it.)
Using configure is certainly a g
On Thu, 01 May 2014 23:06:53 leif wrote:
> François Bissey wrote:
> > On Thu, 01 May 2014 22:58:47 leif wrote:
> >> Felix Salfelder wrote:
> >>> pkg-config --variable pc_path pkg-config
> >>
> >> That doesn't always work. (See my other post on how to get it.)
> >
> > Using configure is certainly
François Bissey wrote:
On Thu, 01 May 2014 22:58:47 leif wrote:
Felix Salfelder wrote:
pkg-config --variable pc_path pkg-config
That doesn't always work. (See my other post on how to get it.)
Using configure is certainly a good option. +1, I like it.
Sage's top-level 'configure' or pkg-
On Thu, 01 May 2014 22:58:47 leif wrote:
> Felix Salfelder wrote:
> > pkg-config --variable pc_path pkg-config
>
> That doesn't always work. (See my other post on how to get it.)
>
>
Using configure is certainly a good option. +1, I like it.
Francois
--
You received this message because you
Felix Salfelder wrote:
pkg-config --variable pc_path pkg-config
That doesn't always work. (See my other post on how to get it.)
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
Francois Bissey wrote:
That's a serious issue that Volker and I have overlooked when pushing
for pkg-config. For those who don't the tipping point for inclusion
was building recent matplotlib in OS X. matplotlib absolutely relies
on using pkgconfig and all the previous work around failed with 1.3
19 matches
Mail list logo