>
> As to the link I gave, the new cryptominisat not only needs C++11
>
Ah, and cryptominisat does need override, i.e. gcc at least 4.7
See https://gcc.gnu.org/projects/cxx0x.html
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
On Tuesday, September 22, 2015 at 7:15:56 AM UTC+2, François wrote:
>
> OK but I don’t think you should hold back personally.
>
It's just a matter of minimizing problems. There is no pressing need
for override in Pynac.
As to the link I gave, the new cryptominisat not only needs C++11
but also, a
On 2015-09-22 05:47, Francois Bissey wrote:
1) Do we want to mandate c++11 support
Y[X] Whenever it's needed by something in Sage
N[X] As long as it's not needed by something in Sage
2) if yes what c++11 features do we want?
Feature complete [ ]
List of features [X]
* Preferably: whatever
On Monday, 21 September 2015 21:42:31 UTC-7, William wrote:
>
> On Mon, Sep 21, 2015 at 7:58 PM, Kwankyu Lee > wrote:
> > I have written a couple of AUTHORS-blocks, but I think I did it not to
> have
> > a credit but to be responsible for the code.
> >
> > AUTHORS blocks are rather for deve
> On 22/09/2015, at 17:13, Ralf Stephan wrote:
>
> On Tuesday, September 22, 2015 at 5:47:39 AM UTC+2, François wrote:
> The 0.4.x branch of pynac needs c++11 and the “override” keyword.
>
> That is not true. I explicitly held back because without
> override gcc 4.6 would suffice.
OK but I do
On Tuesday, September 22, 2015 at 5:47:39 AM UTC+2, François wrote:
>
> The 0.4.x branch of pynac needs c++11 and the “override” keyword.
>
That is not true. I explicitly held back because without
override gcc 4.6 would suffice.
> 1) Do we want to mandate c++11 support
> Y[X]
> N[ ]
Becaus
On Mon, Sep 21, 2015 at 7:58 PM, Kwankyu Lee wrote:
> I have written a couple of AUTHORS-blocks, but I think I did it not to have
> a credit but to be responsible for the code.
>
> AUTHORS blocks are rather for developers, not for end users.
These blocks
> are rather hindrance for end users as th
You are using the read only git url, you need to use the ssh url to be able
to push. You can either add a new remote:
git remote add trac g...@trac.sagemath.org:sage.git
or modify your current remote:
git remote set-url origin g...@trac.sagemath.org:sage.git
On Mon, Sep 21, 2015 at 7:1
We should make a decision on what level of c++ support we want.
The 0.4.x branch of pynac needs c++11 and the “override” keyword.
I don’t think Nathann ever mentioned which c++11 feature he wanted,
he probably just assumed that having a c++11 flag was enough.
Another thing to be cautious of: gcc
On Monday, September 21, 2015 at 6:38:50 PM UTC+2, Volker Braun wrote:
> Afaik we already require C++11 support to compile Pynac
Yes, Pynac git master requires it but we're still installing backported
versions (0.3.9.x vs 0.4.x).
The ticket that never got finished was
http://trac.sagemath.org/t
I have written a couple of AUTHORS-blocks, but I think I did it not to have
a credit but to be responsible for the code.
AUTHORS blocks are rather for developers, not for end users. These blocks
are rather hindrance for end users as they usually appear at the head of a
documentation but these
With some further experimenting I find that I can push from my old copy of
sage (but I can't compile there).
I can edit and compile on one copy of sage and push with another. This is
an awkward setup, but at least I can some edits to a ticket done.
-Mike
On Monday, 21 September 2015 21:57:10 U
You are right that running Xcode did install the command line tools, but
that did not seem to fix the problem.
I continue to get the "fatal: remote error: access denied or repository not
exported: /sage.git" message.
-Mike
On Monday, 21 September 2015 21:21:45 UTC-4, John H Palmieri wrote:
>
>
>
On Monday, September 21, 2015 at 5:54:05 PM UTC-7, Mike Zabrocki wrote:
>
> I mistakenly installed XCode 7 and so to save myself I started working on
> a fresh copy of sage where I don't do too much compiling.
>
Have you tried running Xcode once? It will install some command-line tools,
and th
Does it help to see my .gitconfig file? This hasn't changed though.
[core]
editor = vi
[user]
name = zabrocki
email = zabro...@mathstat.yorku.ca
[alias]
wdiff = diff --color-words
lg = log --graph --pretty=format:'%Cred%h%Creset
-%C(yellow)%d%Creset
$ git remote -v
origin git://trac.sagemath.org/sage.git (fetch)
origin git://trac.sagemath.org/sage.git (push)
On Monday, 21 September 2015 21:02:16 UTC-4, vdelecroix wrote:
>
> How did you configure git? What gives
>
>$ git remote -v
>
> Vincent
>
> On 21/09/15 21:54, Mike Zabrocki
How did you configure git? What gives
$ git remote -v
Vincent
On 21/09/15 21:54, Mike Zabrocki wrote:
I mistakenly installed XCode 7 and so to save myself I started working on a
fresh copy of sage where I don't do too much compiling.
In doing so I seem to have messed up my permissions to ac
I mistakenly installed XCode 7 and so to save myself I started working on a
fresh copy of sage where I don't do too much compiling.
In doing so I seem to have messed up my permissions to access git (or
something). I can checkout any branch I like, but I can't seem to push.
$ git push
fatal: r
On 21 Sep 2015 13:58, "Thierry Dumont" wrote:
>
> Le 21/09/2015 14:16, Jeroen Demeyer a écrit :
> > On 2015-09-21 13:47, Nathann Cohen wrote:
> >> Hello everybody,
> >>
> >> What can we assume on our C compiler? Is it always gcc?
> >
> Did anybody tried ICC ? I can do it, for fun...
For what it
Can someone with an Android system take a look at this? Is it device
specific or the same strange thing happens for everybody?
On Monday, 21 September 2015 11:15:07 UTC-6, Matematica wrote:
>
> I installed SageMath
> https://play.google.com/store/apps/details?id=org.sagemath.droid on my
> phone
On Mon, 21 Sep 2015, Jeroen Demeyer wrote:
Your workflow should look like:
1) checkout ticket or branch
2) make build (or make doc-clean; make)
If you're skipping step 2, it's not surprising that bad things happen.
OK. Before it has more often worked with just ./sage -b and I think that
als
On 2015-09-21 19:23, Bill Janssen wrote:
On OS X, The CasADi subsystem now installs its dynamic
libraries in a subdirectory of JModelica, a subdirectory which then has
to be put on the LD_LIBRARY_PATH the Python interpreter is run with
That is clearly an issue with the build system. Instead of re
I'm updating an old-style JModelica spkg to version 1.16, which just came
out. On OS X, The CasADi subsystem now installs its dynamic libraries in a
subdirectory of JModelica, a subdirectory which then has to be put on the
LD_LIBRARY_PATH the Python interpreter is run with, as CasADi is package
I installed
SageMath https://play.google.com/store/apps/details?id=org.sagemath.droid
on my phone Samsung mini2
http://www.gsmarena.com/samsung_galaxy_mini_2_s6500-3883.php
I get the error from of the attached images. Thanks.
--
You received this message because you are subscribed to the Goog
Afaik we already require C++11 support to compile Pynac
(https://groups.google.com/d/msg/sage-devel/DeT2E8IzTGs/Z_GDKbh06X8J). If
not then we *should* require C++11 because its much better than without...
On Monday, September 21, 2015 at 1:47:17 PM UTC+2, Nathann Cohen wrote:
>
> Hello everybod
On Mon, Sep 21, 2015 at 1:17 AM, Jori Mäntysalo wrote:
> On Mon, 21 Sep 2015, Marc Mezzarobba wrote:
>
>> I agree with that part. It would be wrong to remove the AUTHORS blocks
>> without putting corresponding acklowledgements in an equally prominent
>> place.
>
>
> What if I do a small change? No
On Monday, September 21, 2015, rjf wrote:
>
>
>>
>>
>> >
>> >(Richard) While it is tempting to add every possible tool to Sage,
>> thinking out of the
>> > box can be productive.
>> >
>> > (one answer: there is a bootstrapping problem if you have to have a
>> working
>> > Sage in order to build
>
>
>
> >
> >(Richard) While it is tempting to add every possible tool to Sage,
> thinking out of the
> > box can be productive.
> >
> > (one answer: there is a bootstrapping problem if you have to have a
> working
> > Sage in order to build a working Sage.)
>
> (William)One answer to w
Hi Jeroen,
On 2015-09-21, Jeroen Demeyer wrote:
> On 2015-09-21 11:37, Simon King wrote:
>> Hi!
>>
>> It seems that in the latest beta there was a change in "sage -i"
> Certainly, see
> https://groups.google.com/forum/#!topic/sage-devel/nLDOLvjKp3A
>
>> First it does make -j2 configure.
>>
>> The
On 2015-09-21 15:04, Jori Mäntysalo wrote:
I don't know exactly what has happened, but at least on my systems
compiling is more frequently needed, i.e. sage -b is not enough.
Did you run "make" before (or "make build" if you don't want to wait for
the doc)?
You can use "./sage -b" if, since
On Mon, 21 Sep 2015, Jeroen Demeyer wrote:
Three times is surprising, are you sure you counted correctly? I can
understand 2 (once for the toolchain, once for the package itself), but
3 is a bug. I've just tried with the latest branch at #12103, and I see
"make configure" only twice.
I don't
Le 21/09/2015 14:16, Jeroen Demeyer a écrit :
> On 2015-09-21 13:47, Nathann Cohen wrote:
>> Hello everybody,
>>
>> What can we assume on our C compiler? Is it always gcc?
>
> First of all, compiler choices can always be overridden using SAGE_PORT
> or SAGE_INSTALL_GCC. But let's assume that those
On 2015-09-21 11:37, Simon King wrote:
Hi!
It seems that in the latest beta there was a change in "sage -i"
Certainly, see
https://groups.google.com/forum/#!topic/sage-devel/nLDOLvjKp3A
First it does make -j2 configure.
Then, it does make -j2 configure!
Then, it does make -j2 configure!!
Th
Starting a new thread from a discussion at
https://groups.google.com/d/msg/sage-devel/Jot2ydQjIhk/ZF16lHUzAQAJ
2015-09-17 16:45:53 UTC+2, William:
On Thu, Sep 17, 2015 at 7:34 AM, kcrisman wrote:
>
> > it would be useful to revive the discussion of a
> > true SageMath Foundation, separate fro
On 2015-09-21, Jeroen Demeyer wrote:
> When complaining about a command, could you mention the *exact* command
> you're talking about. I assume it's not just "sage -i"?
./sage -i meataxe
respectively
./sage -i -c meataxe
(working on #12103).
--
You received this message because you are sub
Le mercredi 16 septembre 2015 19:13:42 UTC+2, William a écrit :
Let's plan to have a page describing the compute resources and
> acknowledging *everybody* (or organization) that contributes to having
> bought them, hosting them, and helping to run them.
>
> William
>
We could use
http:/
> Then why didn't you just ask that right away?
- Because I can deduce my answer from the version of GCC (if we always
compile with GCC).
- Because whoever knows the version of GCC may not know if it supports
C++11, and so may not answer.
- Because knowing the version of GCC is of a wider use than
On 2015-09-21 14:12, Nathann Cohen wrote:
I want to know if I can compile c++ files with -std=c++11.
Then why didn't you just ask that right away?
If you're serious about C++11 support, please open a ticket and we can
continue discussing there.
--
You received this message because you are s
>
> Do other people not find it annoying?
I just tried to install a package that was already installed. It takes
around 10 seconds on my computer (I was lucky, it did not try to compare
the speed of all mirrors this time - that takes ages) and filled several
screens with unrelated data. Let'
On 2015-09-21 13:47, Nathann Cohen wrote:
Hello everybody,
What can we assume on our C compiler? Is it always gcc?
First of all, compiler choices can always be overridden using SAGE_PORT
or SAGE_INSTALL_GCC. But let's assume that those variables are undefined.
In that case, you can assume t
>
> I guess the configure script is made to check it is recent enough and
> provides what is needed to build Sage.
> Or at least that it can build our GCC.
>
I want to know if I can compile c++ files with -std=c++11.
Nathann
--
You received this message because you are subscribed to the Googl
On Monday, September 21, 2015 at 1:47:17 PM UTC+2, Nathann Cohen wrote:
>
> Hello everybody,
>
> What can we assume on our C compiler? Is it always gcc? Is it always
> recent?
>
> I guess the configure script is made to check it is recent enough and
provides what is needed to build Sage.
Or a
Hello everybody,
What can we assume on our C compiler? Is it always gcc? Is it always recent?
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+
When complaining about a command, could you mention the *exact* command
you're talking about. I assume it's not just "sage -i"?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send
Hi!
It seems that in the latest beta there was a change in "sage -i" that I
find rather annoying: First it does make -j2 configure. Result: Nothing
to (re)build / all up-to-date. Which takes a couple of seconds
Then, it does make -j2 configure! Result: Sage build/upgrade complete!
Which again tak
On Mon, 21 Sep 2015, Marc Mezzarobba wrote:
I agree with that part. It would be wrong to remove the AUTHORS blocks
without putting corresponding acklowledgements in an equally prominent
place.
What if I do a small change? Not enought to mention, but something
potentially stupid. I don't want
Simon King wrote:
> it is also supposed to say *who* did *what* ("what" meaning the
> purpose/intention of the change)
Commit messages too, and I'd argue they are the right place to do
that...
(Incidentally, I'm not sure git blame would be the right tool if we did
want to auto-generate author i
William Stein wrote:
> If somebody explicitly puts their name in the AUTHORS block when they
> are writing the code in the first place, then we should respect that
> and continue to acknowledge them.
I agree with that part. It would be wrong to remove the AUTHORS blocks
without putting correspond
48 matches
Mail list logo
