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_
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 loo
I think there is on open bug about compilation failures on Solaris which we
never sorted out due to not having access to a test machine.
On Thu, May 28, 2015, 09:13 Bryan Williams
wrote:
> Thanks to the both of you.
>
> First off, apologies for getting back to you several days late. I was out
>
Thanks to the both of you.
First off, apologies for getting back to you several days late. I was out
of town for the holiday weekend, and I didn't get a chance to work on this
for the last two days as I had other business to tend to on Tuesday, and
was out of the office all day Wednesday.
I tried
Bryan,
If you subscribe to the list you will be able to post with out moderation.
Does this happen with any of the other sample data?
I don't think that `get_sample_data` is doing you any good here as you are
passing it an absolute path (from `os.getcwd()`) which is passed into
`os.path.join` wh
Bryan,
First off, avoid importing things from modules that start with an
underscore. Because Python doesn't have semantics for public/private APIs
like C++ and Java does, the underscore is treated as an indicator to
developers that it is to be treated as private. The implication is that we
are fre
