Re: [sage-devel] The Sage dev scripts

[kcrisman]

> > 1) should we keep the "Sage dev" scripts in Sage ? 
> > 2) Should we keep it in the doc ? 
>
> There is one very useful thing in the dev script: transform old 
> mercurial patches into git commit. There are still ticket on trac with 
> patches and I use this tool from time to time. 
>
>
Oh!  I didn't know that - I have wasted a lot of time then doing that "by 
hand"! 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Deprecate fast_float?

[kcrisman]

On Friday, January 9, 2015 at 4:10:41 PM UTC-5, Andrey Novoseltsev wrote:
>
> Hello,
>
> I got 0^(2/3) = 1 as a result of fast_float. Trying to see what is wrong 
> with it, I found out that nobody worked on that file since 2010 and 
> fast_callable is a better replacement for it. Here is an example:
>
>
See e.g. http://trac.sagemath.org/ticket/15030 and 
http://trac.sagemath.org/ticket/8450 but 
see http://trac.sagemath.org/ticket/5572 for problems.  For something on 
your side, see http://trac.sagemath.org/ticket/13559 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Deprecate fast_float?

[Andrey Novoseltsev]

Thanks for catching that - so it is faster, but it is wrong.

fast_callable gives wrong answer for float and RDF domains, but correct one 
for RR... Which is quite annoying since 0^(2/3) does not look like an 
ambiguous expression to me.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Deprecate fast_float?

[Robert Bradshaw]

On Fri, Jan 9, 2015 at 1:10 PM, Andrey Novoseltsev  wrote:
> Hello,
>
> I got 0^(2/3) = 1 as a result of fast_float. Trying to see what is wrong
> with it, I found out that nobody worked on that file since 2010 and
> fast_callable is a better replacement for it. Here is an example:
>
> sage: f(x) = (x+1)^(2/3)
> sage: print f(1), f(-1)
> 2^(2/3) 0
> sage: timeit("f(1)")
> 625 loops, best of 3: 169 µs per loop
> sage: timeit("f(-1)")
> 625 loops, best of 3: 67 µs per loop
> sage: fc = fast_callable(f, vars=["x"])
> sage: print fc(1), fc(-1)
> 2^(2/3) 0
> sage: timeit("fc(1)")
> 625 loops, best of 3: 60.9 µs per loop
> sage: timeit("fc(-1)")
> 625 loops, best of 3: 10.8 µs per loop
>
> sage: ff = fast_float(f, "x")
> sage: print ff(1), ff(-1)
> 1.58740105197 1.0 # WRONG!!!
>
> sage: timeit("f(1)")
> 625 loops, best of 3: 169 µs per loop
> sage: timeit("f(-1)")
> 625 loops, best of 3: 67.1 µs per loop
>
> So fast_callable is both correct and faster. Should we then deprecate
> fast_float and switch all internal calls to fast_callable?

You'r timing f, not ff here.

sage: f(x) = (x+1)^(2/3)
sage: ff = fast_float(f, "x")
sage: sage: timeit("ff(1)")
625 loops, best of 3: 635 ns per loop
sage: sage: timeit("ff(-1)")
625 loops, best of 3: 479 ns per loop

Note that fact callable takes a domain.

sage: fc = fast_callable(f, vars=["x"])
sage: fc(-1)
0

sage: fc = fast_callable(f, vars=["x"], domain=RR)
sage: fc(-1)
0.000

sage: fc = fast_callable(f, vars=["x"], domain=float)
sage: fc(-1)   # that's what you get...
1.0

FWIW, I'm all for deleting fast_float once its successor is superior
in all regards (which it might be at this point).

- Robert

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Deprecate fast_float?

[Andrey Novoseltsev]

Hello,

I got 0^(2/3) = 1 as a result of fast_float. Trying to see what is wrong 
with it, I found out that nobody worked on that file since 2010 and 
fast_callable is a better replacement for it. Here is an example:

sage: f(x) = (x+1)^(2/3)
sage: print f(1), f(-1)
2^(2/3) 0
sage: timeit("f(1)")
625 loops, best of 3: 169 µs per loop
sage: timeit("f(-1)")
625 loops, best of 3: 67 µs per loop
sage: fc = fast_callable(f, vars=["x"])
sage: print fc(1), fc(-1)
2^(2/3) 0
sage: timeit("fc(1)")
625 loops, best of 3: 60.9 µs per loop
sage: timeit("fc(-1)")
625 loops, best of 3: 10.8 µs per loop

sage: ff = fast_float(f, "x")
sage: print ff(1), ff(-1)
1.58740105197 1.0 # WRONG!!!

sage: timeit("f(1)")
625 loops, best of 3: 169 µs per loop
sage: timeit("f(-1)")
625 loops, best of 3: 67.1 µs per loop

So fast_callable is both correct and faster. Should we then deprecate 
fast_float and switch all internal calls to fast_callable?

Thank you,
Andrey

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Installing gap_packages on mac

[anurag bishnoi]

On Friday, 9 January 2015 19:36:40 UTC+1, David Joyner wrote:
>
> On Fri, Jan 9, 2015 at 10:53 AM, anurag bishnoi  > wrote: 
> > I am trying to install the gap_packages in my sage installation so that 
> I 
> > can construct the McLaughlinGraph which uses the design package of GAP. 
> > 
>

> You can do this by hand: 
> (1) Go to the GAP website (gap-system.org), 
> (2) Find the design package (which has no binary component, BTW), 
> (3) Save it to 
> .../sage-6.4.rc0/local/gap/gap-4.7.5/pkg 
> Unpack it 
> (4) Start sage and load the package design via GAP. 
>
>
Thanks. That worked. :)
 

>
> > I tried the instructions mentioned here: 
> > http://wiki.sagemath.org/InstallingGapPackages, and got the following 
> error, 
> > 
> > " 
> > 
> > checking whether the C compiler (gcc  ) works... no 
> > 
> > configure: error: installation or configuration problem: C compiler 
> cannot 
> > create executables. 
> > " 
> > 
> > I have attached the full log file. 
> > 
> > I am using an iMac with OS X 10.9.5 (13F34) installed on it. 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at http://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Installing gap_packages on mac

[David Joyner]

On Fri, Jan 9, 2015 at 10:53 AM, anurag bishnoi  wrote:
> I am trying to install the gap_packages in my sage installation so that I
> can construct the McLaughlinGraph which uses the design package of GAP.
>


You can do this by hand:
(1) Go to the GAP website (gap-system.org),
(2) Find the design package (which has no binary component, BTW),
(3) Save it to
.../sage-6.4.rc0/local/gap/gap-4.7.5/pkg
Unpack it
(4) Start sage and load the package design via GAP.


> I tried the instructions mentioned here:
> http://wiki.sagemath.org/InstallingGapPackages, and got the following error,
>
> "
>
> checking whether the C compiler (gcc  ) works... no
>
> configure: error: installation or configuration problem: C compiler cannot
> create executables.
> "
>
> I have attached the full log file.
>
> I am using an iMac with OS X 10.9.5 (13F34) installed on it.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Installing gap_packages on mac

[anurag bishnoi]

I am not sure I remember now how I installed SAGE on this system. Probably 
it was already there when I started using it. 
I have been using SAGE for past one year without any issues. 
Here's what happens with those commands: 


pccage35:Code bishnoi$ sage -sh

Starting subshell with Sage environment variables set.  Don't forget

to exit when you are done.  Beware:

 * Do not do anything with other copies of Sage on your system.

 * Do not use this for installing Sage packages using "sage -i" or for

   running "make" at Sage's root directory.  These should be done

   outside the Sage shell.


Bypassing shell configuration files...


Note: SAGE_ROOT=/Applications/sage

(sage-sh) bishnoi@pccage35:Code$ exit

exit

Exited Sage subshell.

pccage35:Code bishnoi$ 

pccage35:Code bishnoi$ which gcc

/usr/bin/gcc

pccage35:Code bishnoi$ gcc --version 

Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/c++/4.2.1

Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)

Target: x86_64-apple-darwin13.4.0

Thread model: posix

pccage35:Code bishnoi$ 

On Friday, 9 January 2015 17:34:00 UTC+1, kcrisman wrote:
>
>
> I am trying to install the gap_packages in my sage installation so that I 
>> can construct the McLaughlinGraph which uses the design package of GAP. 
>>
>> I tried the instructions mentioned here: 
>> http://wiki.sagemath.org/InstallingGapPackages, and got the following 
>> error,
>>
>> " 
>>
>> checking whether the C compiler (gcc  ) works... no
>>
>> configure: error: installation or configuration problem: C compiler 
>> cannot create executables.
>> "
>>
>>
> It looks like you have just a binary of Sage that you did not compile 
> yourself, is that right?  I assume you do not have Xcode or the Command 
> Line Tools?  Also, what happens if you type
>
> $ sage -sh
> $ which gcc
> $ gcc --version 
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] The Sage dev scripts

[Vincent Delecroix]

> 1) should we keep the "Sage dev" scripts in Sage ?
> 2) Should we keep it in the doc ?

There is one very useful thing in the dev script: transform old
mercurial patches into git commit. There are still ticket on trac with
patches and I use this tool from time to time.

Vincent

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: The Sage dev scripts

[Volker Braun]

On Friday, January 9, 2015 at 5:10:03 PM UTC+1, martin@gmx.net wrote:
>
> Hadn't known of git-trac before. Since the tool has some sage settings 
> hard-wired into it, perhaps it should be called git-sage instead, to avoid 
> clashes?
>

My goal was to keep git-trac as independent as possible from Sage. There 
are only few Sage-specific things in there, but (like trac 
username/password) could be moved to configuration options inside the repo. 
I was hoping that our git + track setup would end up being useful for other 
projects as well.

 Reading the documentation now for the first time, some things are not 
> perfectly clear. For example, when creating a ticket, where does the ticket 
> description come from?


Tickets are created without description. You need a web browser for that. 
New tickets don't have a branch attached.

The printed code snippet doesn't show it, and the text doesn't mention it. 
> The text also doesn't say where the content of the remote branch comes 
> from. So should I do this step at a point where I already have some 
> modifications locally, or can I do this at any time?


If you already have modifications that are not in a separate branch then 
put them in a local branch. Ideally, get in the habit of starting a new 
branch before making changes.

If you aleready have commits in a local branch you can just "git trac push 
"  (where  = ticket number)

You can create a new local branch with "git trac checkout "

 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Installing gap_packages on mac

[kcrisman]

> I am trying to install the gap_packages in my sage installation so that I 
> can construct the McLaughlinGraph which uses the design package of GAP. 
>
> I tried the instructions mentioned here: 
> http://wiki.sagemath.org/InstallingGapPackages, and got the following 
> error,
>
> " 
>
> checking whether the C compiler (gcc  ) works... no
>
> configure: error: installation or configuration problem: C compiler cannot 
> create executables.
> "
>
>
It looks like you have just a binary of Sage that you did not compile 
yourself, is that right?  I assume you do not have Xcode or the Command 
Line Tools?  Also, what happens if you type

$ sage -sh
$ which gcc
$ gcc --version 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Installing gap_packages on mac

[John H Palmieri]

Did you build Sage from source, or did you get a binary distribution?

On Friday, January 9, 2015 at 7:53:46 AM UTC-8, anurag bishnoi wrote:
>
> I am trying to install the gap_packages in my sage installation so that I 
> can construct the McLaughlinGraph which uses the design package of GAP. 
>
> I tried the instructions mentioned here: 
> http://wiki.sagemath.org/InstallingGapPackages, and got the following 
> error,
>
> " 
>
> checking whether the C compiler (gcc  ) works... no
>
> configure: error: installation or configuration problem: C compiler cannot 
> create executables.
> "
>
> I have attached the full log file. 
>
> I am using an iMac with OS X 10.9.5 (13F34) installed on it. 
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: The Sage dev scripts

[martin . vgagern]

Hadn't known of git-trac before. Since the tool has some sage settings 
hard-wired into it, perhaps it should be called git-sage instead, to avoid 
clashes?

Recently I've been using git the hard way for pretty much everything except 
pushing, for which I used "./sage -dev push --ticket" in the hope that that 
will take care of setting any fields on the Trac ticket that need setting. 
I had been using the dev scripts more at first, but the mapping between 
tickets and branch names was a real pain, so anything which can simply 
deduce the ticket number from the branch name sounds like a good thing to 
have. Seems I'll have to learn a new way now, but the change seems simple 
enough.

Reading the documentation now for the first time, some things are not 
perfectly clear. For example, when creating a ticket, where does the ticket 
description come from? The printed code snippet doesn't show it, and the 
text doesn't mention it. The text also doesn't say where the content of the 
remote branch comes from. So should I do this step at a point where I 
already have some modifications locally, or can I do this at any time? Does 
it matter what branch I'm on locally? What's the point of creating a remote 
branch if I don't have any code at this point? The note about how I could 
also open a ticket using my web browser is already in the next section, 
which is confusing.

The “Finishing Up” section isn't perfectly clear either. It mentions “the 
trac server”, but that could be the git server associated with trac or the 
trac web interface as opened in a browser. I assume the latter. In which 
case I'd add my name into the “Authors” field accessible under the “Modify 
Ticket” section, just as the ticket status is. The note about “first line” 
is confusing to me. The “Merging” section gives special consideration to 
the “master” branch, but shouldn't the same consideration also apply to the 
“develop” branch? Perhaps that section should also discuss the dependencies 
field for Trac tickets, since when one ticket merges code from another, 
you'd usually want it to depend on that other as well. You might also want 
to offer some guideline about the converse: if some code depends on some 
other code, should you merge branches even though doing so will add code to 
the diff? In #16571  I decided not 
to do so, but I had been reading the docs (for the dev scripts) searching 
for some guideline on this.

So if you want to rewrite the documentation some more, you might want to 
address some of these things.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Installing gap_packages on mac

[anurag bishnoi]

I am trying to install the gap_packages in my sage installation so that I 
can construct the McLaughlinGraph which uses the design package of GAP. 

I tried the instructions mentioned 
here: http://wiki.sagemath.org/InstallingGapPackages, and got the following 
error,

" 

checking whether the C compiler (gcc  ) works... no

configure: error: installation or configuration problem: C compiler cannot 
create executables.
"

I have attached the full log file. 

I am using an iMac with OS X 10.9.5 (13F34) installed on it. 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


gap_packages.log
Description: Binary data

Re: [sage-devel] Re: Bug Days?

[mmarco]

If it is in July, i would be happy to give a hand. Befire that would be 
impossible for me because of my teaching duties.

El jueves, 8 de enero de 2015, 17:27:45 (UTC+1), William escribió:
>
> On Thu, Jan 8, 2015 at 8:20 AM, kcrisman > 
> wrote: 
> >> 
> >> 
> >> Would anybody be interested in helping me to organize a bug days 
> >> workshop sometime in the next few months? 
> >> 
> > 
> > Can you define "next few months", e.g. does it mean before the end of 
> > typical US academic year calendars or into the summer as well? 
>
> Before August 2015. 
>
>  -- William 
>
>
> -- 
> William Stein 
> Professor of Mathematics 
> University of Washington 
> http://wstein.org 
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Build error for sage 6.4 beta 5 under cygwin64

[kcrisman]

>
> That is easy to fix.
> Just add gmp to the linked libraries in module_list.py for these files.
> People should really pay attention to what they use in their code, Linux 
> is just too nice.
>

This is a very, very typical Cygwin-type fix, adding additional libraries 
to module_list.py - but until we have a buildbot for Cygwin, it's going to 
continue. 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Build error for sage 6.4 beta 5 under cygwin64

[Jean-Pierre Flori]

On Friday, January 9, 2015 at 9:49:52 AM UTC+1, Sebastien Gouezel wrote:
>
> The webpage http://trac.sagemath.org/wiki/Cygwin64Port indicates that 
> sage can now be built under cygwin64 almost out of the box. So, I tried, 
> but I failed... 
>
> Here are the problems I encountered, maybe someone with better computer 
> skills can see what is going on. My sage version is sage 6.4beta5 with 
> #17365 pulled. Very recent cygwin64  


> - First, pyzmq did not compile, because of undefined references in 
> libzmq.a. It seems that the flag -no-undefined was not passed to ld 
> while building libzmq.a (despite #17333). I hacked the makefile to make 
> sure that the flag was passed when compiling zeromq, this solved the 
> issue. 
>
> Note that "-no-undefined" is a libtool flag, not an ld one.
I'll try to have a look next week asI'll be in the wild for more than a 
month after that.

- Then, while compiling sage proper, I get the following error 
>
> gcc -I/usr/include/ncurses -fno-strict-aliasing -g -O2 -DNDEBUG -g 
> -fwrapv -O3 -Wall -I/home/Sebastien/sage/local/include 
> -I/home/Sebastien/sage/local/include/csage -I/home/Sebastien/sage/src 
> -I/home/Sebastien/sage/src/sage/ext 
> -I/home/Sebastien/sage/local/include/python2.7 -c 
> build/cythonized/sage/graphs/distances_all_pairs.c -o 
> build/temp.cygwin-1.7.33-x86_64-2.7/build/cythonized/sage/graphs/distances_all_pairs.o
>  
>
> -fno-strict-aliasing -w -fno-tree-dominator-opts 
>
> gcc -shared -Wl,--enable-auto-image-base 
> -L/home/Sebastien/sage/local/lib 
> build/temp.cygwin-1.7.33-x86_64-2.7/build/cythonized/sage/graphs/distances_all_pairs.o
>  
>
> -L/home/Sebastien/sage/local/lib 
> -L/home/Sebastien/sage/local/lib/python2.7/config 
> -L/home/Sebastien/sage/local/lib -lcsage -lpython2.7 -o 
> build/lib.cygwin-1.7.33-x86_64-2.7/sage/graphs/distances_all_pairs.dll 
>
> build/temp.cygwin-1.7.33-x86_64-2.7/build/cythonized/sage/graphs/distances_all_pairs.o:
>  
>
> dans la fonction « 
> __pyx_f_4sage_6graphs_19distances_all_pairs_bitset_clear »: 
>
> /home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010:
>  
>
> référence indéfinie vers « __imp___gmpn_zero » 
>
> /home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010:(.text+0x1493):
>  
>
> relocalisation tronquée pour concorder avec la taille: R_X86_64_PC32 
> vers le symbole indéfini __imp___gmpn_zero 
>
> /home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010:
>  
>
> référence indéfinie vers « __imp___gmpn_zero » 
>
> /home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010:(.text+0xba8e):
>  
>
> relocalisation tronquée pour concorder avec la taille: R_X86_64_PC32 
> vers le symbole indéfini __imp___gmpn_zero 
>
> That is easy to fix.
Just add gmp to the linked libraries in module_list.py for these files.
People should really pay attention to what they use in their code, Linux is 
just too nice.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Build error for sage 6.4 beta 5 under cygwin64

[Sebastien Gouezel]

The webpage http://trac.sagemath.org/wiki/Cygwin64Port indicates that 
sage can now be built under cygwin64 almost out of the box. So, I tried, 
but I failed...


Here are the problems I encountered, maybe someone with better computer 
skills can see what is going on. My sage version is sage 6.4beta5 with 
#17365 pulled. Very recent cygwin64


- First, pyzmq did not compile, because of undefined references in 
libzmq.a. It seems that the flag -no-undefined was not passed to ld 
while building libzmq.a (despite #17333). I hacked the makefile to make 
sure that the flag was passed when compiling zeromq, this solved the issue.


- Then, while compiling sage proper, I get the following error

gcc -I/usr/include/ncurses -fno-strict-aliasing -g -O2 -DNDEBUG -g 
-fwrapv -O3 -Wall -I/home/Sebastien/sage/local/include 
-I/home/Sebastien/sage/local/include/csage -I/home/Sebastien/sage/src 
-I/home/Sebastien/sage/src/sage/ext 
-I/home/Sebastien/sage/local/include/python2.7 -c 
build/cythonized/sage/graphs/distances_all_pairs.c -o 
build/temp.cygwin-1.7.33-x86_64-2.7/build/cythonized/sage/graphs/distances_all_pairs.o 
-fno-strict-aliasing -w -fno-tree-dominator-opts


gcc -shared -Wl,--enable-auto-image-base 
-L/home/Sebastien/sage/local/lib 
build/temp.cygwin-1.7.33-x86_64-2.7/build/cythonized/sage/graphs/distances_all_pairs.o 
-L/home/Sebastien/sage/local/lib 
-L/home/Sebastien/sage/local/lib/python2.7/config 
-L/home/Sebastien/sage/local/lib -lcsage -lpython2.7 -o 
build/lib.cygwin-1.7.33-x86_64-2.7/sage/graphs/distances_all_pairs.dll


build/temp.cygwin-1.7.33-x86_64-2.7/build/cythonized/sage/graphs/distances_all_pairs.o: 
dans la fonction « 
__pyx_f_4sage_6graphs_19distances_all_pairs_bitset_clear »:


/home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010: 
référence indéfinie vers « __imp___gmpn_zero »


/home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010:(.text+0x1493): 
relocalisation tronquée pour concorder avec la taille: R_X86_64_PC32 
vers le symbole indéfini __imp___gmpn_zero


/home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010: 
référence indéfinie vers « __imp___gmpn_zero »


/home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010:(.text+0xba8e): 
relocalisation tronquée pour concorder avec la taille: R_X86_64_PC32 
vers le symbole indéfini __imp___gmpn_zero


collect2: erreur: ld a retourné 1 code d'état d'exécution

Looks like a problem with mpir, or a linking problem... I can give more 
details or log files if needed.



Sebastien

--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.