[beports] Re: python2.5.2

On Sat, Aug 16, 2008 at 2:52 PM, Andreas Färber <andreas.faerber@xxxxxx> wrote:
> Hi Scott,
>
> Am 15.08.2008 um 21:44 schrieb scott mc:
>
>> I was able to get python2.5.2 to build yesterday and posted an updated
>> portlog entry and updated Andreas patch, but not sure it's working
>> right, still need to try running some more tests.  Some things work,
>> others don't, not sure why yet.  I was able to use it to build pygame,
>> but pygame isn't working correctly either.
>
> Unfortunately, http://ports.haiku-files.org/wiki/dev-lang/python/2.5.2/1
> does not log what exactly the difference is between our patches. I did mine
> on the SVN branch, you presumably against the latest stable release. Did you
> add/remove anything, apart from config.* etc. and ld_so_haiku? The latter
> sounds like a good idea, we probably still had BeOS-compatible libnet when I
> created my patch. Some things in my patch were not too pretty (for upstream)
> but were added to quickly get it working.
>
> I know we have different views on the workflow, so for the record there
> were/are already betas of 2.6. I have no idea how fast that is going to be
> declared stable, but then again I don't have any idea either how long it'd
> take to fix "everything". I did my patch on the 2.5.x branch to avoid the
> beta-ness as source of errors; currently I'm trying to push things out of my
> patch queue before the end of the month, so I might get a copy of the 2.6
> branch (using Bazaar if it works?) and start applying the changes there so
> we can start getting some of them in. For your stable patch it shouldn't
> matter for instance whether Haiku is on a new line or not. And it does not
> seem possible to make all modules work on Haiku anytime soon because some
> features are simply not available, so I'd say any initial patches accepted
> for Haiku support would be good for us.
>
> Andreas
>
> --

Andreas,
I say go for it.  They are working on py3k which is "supposed" to be
ready by October, at which point they are supposed to also release 2.6
which will be end of life of 2.x python.  The 2.6 is supposed to issue
warnings where code would fail on py3k.  Seems to me bzr was an easy
compile months ago, but was done before i was saving the binaries.
Should be an easy one.  Yes your python 2.5.x was done before Haiku
switched from -lnet to -lnetwork which is why i needed to do a new fix
for that.   Anyways I'll let you work on python as it's huge and a bit
over my head in places.
Same with cmake.  I think cmake is close where i left it but theres a
few more __BEOS__ cases that just might be what's tripping it up.
Perhaps the patch i have created so far for it can be broken up like
you did with git so they can be applied upstream, where we are sure of
each of them.  Might be that i did the wrong thing in a few place
even, i'm not sure as sometimes i was just guessing whether to put in
__HAIKU__ or !defined __HAIKU__.
I'm now working on native hardware since trying the ata driver in
place of the ide one, so i'm going to focus on the media libs again
and try to knock out them out.  Programs like vlc rely on many of
these so i'll going to work on their lower level dependencies,
Yasm compiled without too much effort but when i tried to build
xvidcore it tripped on some assembly code, i need to to check yasm to
make sure it's working first.  Too bad not all of these include tests
to verify them.
-scott
--
HaikuPorts homepage - http://ports.haiku-files.org
List archives: http://www.freelists.org/archives/beports
Administrative contact: brecht@xxxxxxxxxxx

Other related posts: