"Eric J. Schwertfeger" <[EMAIL PROTECTED]> writes:
> I'll help out as best I can, but aside from typing ./configure, my
> autoconf skill is nill. As for patches to the source, I'm willing, I'm
> just not sure about Big Brother's take on a US citizen helping an overseas
> crypto project, even if the patches don't touch the actual crypto code.
I'm no expert on US law. If you feel that patches are off limits, a
reasonably detailed description of the needed changes should do fine
as well.
> And how would you like it? It's my lunch break, so I'm going through the
> whole process again, capturing it with script, doing any editing in a
> seperate xterm, but diffing the changes. gzipped, off the list?
If it's not too huge (which I hope is the case), I think the list is
the right place. Otherwise, you can send it directly to me. Preferably
plain text, not zipped, but that doesn't matter very much.
> According to the man pages for getsockopt, FreeBSD 3.3 and Solaris 2.6
> expect *int (so the variable would be int) and Unixware 4.2MP/2.1.3
> expects *size_t.
Are these two types the same on any of those systems? It would make
things easier with a single fallback type.
> The .x file was there, the .xT wasn't (the above line, with the false, is
> what I was referring to). I think I just figured it out, when I modify
> spki.c to allow for sys/time.h, it gets caught in the dependancies.
> Confirmed, when I touch spki.c back to the original time, the compile goes
> fine without needing scsh. O.K., didn't think of trying to fix
> complie-time errors as hacking, but as far as the computer's concerned, it
> is.
.xT are temporaries, they are just there to make sure that the
.x-files are updated atomically. No make dependency mention any .xT
file.
Thanks for the help,
/Niels
