Re: lang/python and NO_SHARED_ARCHS support

2006-01-27 Thread Peter Valchev
Currently it does not get built in fact, because databases/db is marked as NO_SHARED by default, which seems a bit dumb.

Re: lang/python and NO_SHARED_ARCHS support

2006-01-27 Thread Marc Balmer
* Matthieu Herrb wrote: > Marc Balmer wrote: > >* Aleksander Piotrowski wrote: > > > > > >>I would like to drop support for NO_SHARED_ARCHS (right now that would be > >>m88k and > >>vax) to make lang/python port easier to maintain. Right now it's PITA > >>to change anything in this port and of co

Re: lang/python and NO_SHARED_ARCHS support

2006-01-27 Thread Matthieu Herrb
Marc Balmer wrote: * Aleksander Piotrowski wrote: I would like to drop support for NO_SHARED_ARCHS (right now that would be m88k and vax) to make lang/python port easier to maintain. Right now it's PITA to change anything in this port and of course I don't have m88k or vax to check if it sti

Re: lang/python and NO_SHARED_ARCHS support

2006-01-27 Thread Marc Balmer
* Aleksander Piotrowski wrote: > I would like to drop support for NO_SHARED_ARCHS (right now that would be > m88k and > vax) to make lang/python port easier to maintain. Right now it's PITA > to change anything in this port and of course I don't have m88k or vax > to check if it still works OK o

lang/python and NO_SHARED_ARCHS support

2006-01-27 Thread Aleksander Piotrowski
Hi I would like to drop support for NO_SHARED_ARCHS (right now that would be m88k and vax) to make lang/python port easier to maintain. Right now it's PITA to change anything in this port and of course I don't have m88k or vax to check if it still works OK on them (; Any opinions? Alek -- It