On Sun, Aug 09, 2009 at 07:15:09PM +0300, Kalle Olavi Niemitalo wrote:
> Edd Barrett <vex...@gmail.com> writes:
> > My next question is, how hard is it to put this back into the stable
> > branch?
> This patch itself wouldn't be too hard to apply to elinks-0.11.
I don't think I have the time to do so. Will you be planning to do this
anyway? I think it would be wise, given that *all* sparc64 machines
independent of platform will be unusable.
> A much simpler patch is also possible if we can assume that
> casting function pointers or integers to data pointers and back
> preserves the values. (POSIX guarantees this for function
> pointers but ELinks has been run in non-POSIX systems in the
> past. AFAIK, nothing guarantees this for data pointers.)
Is there such a thing as a POSIX compatible system? :P
Do you have a patch? I could try it on OpenBSD, which is mostly POSIX
> However, some other parts of bug 764 have already been fixed in
> elinks-0.12. So we'd first need to make a list of those commits and
> backport them. Commit 1ec1dc43be13e062e18368bf05928ac95d7b7ba5 is
> one of them for sure.
Just out of interest, how stable is elinks "unstable". As a rule of
thumb OpenBSD would not accept "unstable" code, but maybe if backporting
will be painful, it could be possible to use a snapshot for our packages
(Freelance software developer / technical writer / open-source developer)
elinks-dev mailing list