[tahoe-dev] [pycryptopp] #22: pycryptocpp won't build on OpenSolaris 0906

[pycryptopp]

#22: pycryptocpp won't build on OpenSolaris 0906
------------------------+---------------------------------------------------
     Reporter:  bewst   |      Owner:        
         Type:  defect  |     Status:  closed
     Priority:  major   |    Version:  0.5.1 
   Resolution:  fixed   |   Keywords:        
Launchpad_bug:          |  
------------------------+---------------------------------------------------

Comment(by zooko):

 Great!  Thanks!  Here's what you do:

 1.  Install buildbot -- http://buildbot.net
 2.  Choose a name for your machine which will distinguish it from the
 following set: ['slave-gutsy-tahoe', 'faust-osx', 'zandr-64',
 'buildbot.rubenkerkhof.com', 'tahoeslave-feisty', 'windows-cygwin-tahoe',
 'windows-native-tahoe', 'virtual1-edgy-tahoe', 'slave-etch-tahoe',
 'draco', 'gutsy', 'luther-dsl', 'windows-native', 'solaris-amd64-nexenta-
 nooxie', 'linux-amd64-ubuntu-hardy-yukyuk', 'slave-osx-leopard', 'nooxie-
 opensolaris', 'yukyuk', 'buildslave at tahoecs2/slave-speed-colo',
 'mac-i386-osx-10.5-faust', 'slave1-testing-tahoe', 'mac-
 amd64-osx-10.4.11-ootles', 'zandr-linkstation', 'mac-
 amd64-osx-10.5-virtualzooko', 'slave3-dapper', 'windows-cygwin', 'slave3
 -dapper-tahoe']
 3.  Send your buildslave name and a secret password to zooko at zooko.com .
 4.  Run "buildbot create-slave $DIRECTORY dev.allmydata.com:10998
 $BUILDSLAVENAME $BUILDSLAVEPASSWORD
 5.  Run "buildbot start $DIRECTORY"

 Optionally then set up a buildslave to test Tahoe itself in addition to
 the one that you just set up to test pycryptopp: make a different
 directory and run the same steps as above but with master =
 dev.allmydata.com:9987 instead of dev.allmydata.com:10998.  You can use
 the same buildslavename and password for both.

-- 
Ticket URL: <http://allmydata.org/trac/pycryptopp/ticket/22#comment:3>
pycryptopp <http://allmydata.org/trac/pycryptopp>
Python bindings for the Crypto++ library