It seems like it is a conflict of libraries...I've zeroed in to these two errors:
/usr/include/unistd.h:496:75: error: conflicting declaration of C function 'void swab(const void*, void*, ssize_t)' and /usr/include/stdlib.h:144:13: note: previous declaration 'void swab(const char*, char*, ssize_t)' I executed a find command and here's what came up: ~>sudo find / -name stdlib.h */opt/csw/include/c++/4.9.2/tr1/stdlib.h* /opt/solarisstudio12.4/lib/compilers/include/CC/gnu/stdlib.h /opt/solarisstudio12.4/lib/compilers/include/CC/stlport4/stdlib.h /opt/solarisstudio12.4/lib/compilers/CC-gcc/include/c++/4.8.2/tr1/stdlib.h */usr/include/stdlib.h* >From what it seems, it's calling stdlib.h from the /usr/include folder when it should be calling it from /opt/csw/include. I'm going to look into setup.cfg (that or perhaps hack setup.py) and see if it's at all possible to change it so that it looks in the right one, and then I'll try building it again. On Thu, May 28, 2015 at 1:50 PM, Eric Firing <efir...@hawaii.edu> wrote: > On 2015/05/28 3:13 AM, Bryan Williams wrote: > > I have gcc on the box. I also installed the C compiler for Solaris (cc), > > but I couldn't seem to find an option to switch it so that it uses cc > > rather than gcc. > > Maybe you can do this with an environment variable? > > export CC=/usr/bin/cc > > It does look like there is a problem with scrambled environments. The > redefinition warning looks potentially troublesome; and the error looks > like a conflict between two versions of the standard C library. > > From "man swab" on Solaris: > > NAME > swab - swap bytes > > SYNOPSIS > #include <stdlib.h> > > void swab(const char *src, char *dest, ssize_t nbytes); > > XPG4, SUS, SUSv2, SUSv3 > #include <unistd.h> > > void swab(const void *restrict src, void *restrict dest, > ssize_t nbytes); > > I think you want the second version, consistently, but something is also > hitting the first version. > > Maybe "XPG4" or one of the other 4 options needs to be defined when each > library is compiled with /usr/bin/cc? I think the stdlib declaration is > old; the unistd version is more modern. > > That's all very vague, I know. Obviously, I don't actually know how to > solve the problem. > > Eric > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Matplotlib-users mailing list > Matplotlib-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >
------------------------------------------------------------------------------
_______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
