Nicolas M. Thiery wrote:
> On Thu, Nov 12, 2009 at 09:34:10PM +1300, François Bissey wrote:
>> On Thu, 12 Nov 2009 19:27:51 Jason Grout wrote:
>>> William Stein wrote:
>>>> Dear Jason,
>>>>
>>>> The Nauty spkg is broken with modern GCC's.  You're spkg maintainer
>>>> for that package, so I'm letting you know:
>>>>
>>>>    http://trac.sagemath.org/sage_trac/ticket/7439
>>>>
>>>> Of course, if anybody wants to fix this it would be awesome!
>>> I confirmed that this is a problem with the latest nauty 2.4 as well.
>>> I've sent a message to the nauty mailing list.
>>>
>> That's a fairly well known kind of issue. getline has made it in the libc 
>> standard and is now in glibc. The problem is getline is a fairly common
>> name for a custom function... So clash ensue. Two solutions:
>> * if the getline form glibc does what you want migrate to it.
>> *simpler just rename the function to nauty_getline for example
>> a grep will locate every occurrence and a sed will take care of the rest.
>> I can cook a patch that way if you want when I have time.
> 
> We got the same problem in our Nauty module in MuPAD-Combinat, and
> just added a:
> 
>       #define getline getline_nauty_in_mupad
> 
> just before the definition of getline in gtools.h. That makes for a
> more localized patch.
> 


That is basically what Brendan said:

http://dcsmail.anu.edu.au/pipermail/nauty-list/2009-November/000546.html

Thanks,

Jason



-- 
Jason Grout


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to