On Aug 28, 7:19 pm, "Stephen Hartke" <[EMAIL PROTECTED]> wrote:
> My understanding is that nauty is not intended to be built into a library,
> and hence this is why -fPIC is not used. Is there any reason to not use
> -fPIC for a statically linked executable (as nauty is normally used)?
Code comp
On Thu, Aug 28, 2008 at 5:13 PM, mabshoff <[EMAIL PROTECTED]> wrote:
> On Aug 28, 2:54 pm, Jason Grout <[EMAIL PROTECTED]> wrote:
> > > The Python extension is linked against nauty object files, and gcc
> > > complains these should be compiled with the flag "-fPIC" to make
> > > relocatable code.
On Thu, Aug 28, 2008 at 4:59 PM, mabshoff <[EMAIL PROTECTED]> wrote:
> > The Python extension is linked against nauty object files, and gcc
> complains
> > these should be compiled with the flag "-fPIC" to make relocatable code.
> > nauty does not have this flag normally, so I modified the makefil
On Aug 28, 2:54 pm, Jason Grout <[EMAIL PROTECTED]> wrote:
Hi,
> Stephen Hartke wrote:
> > I've added my Python binding for nauty into Jason Grout's optional nauty
> > spkg. (Jason: I hope that's okay. Since the extension needs to include
> > nauty and link against it, it seems simplest to in
On Aug 28, 1:20 pm, "Stephen Hartke" <[EMAIL PROTECTED]> wrote:
Hi Stephen,
> I've added my Python binding for nauty into Jason Grout's optional nauty
> spkg. (Jason: I hope that's okay. Since the extension needs to include
> nauty and link against it, it seems simplest to include it in one pac
Stephen Hartke wrote:
> I've added my Python binding for nauty into Jason Grout's optional nauty
> spkg. (Jason: I hope that's okay. Since the extension needs to include
> nauty and link against it, it seems simplest to include it in one
> package.) It can be downloaded at
> http://www.math.un
