[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Where to from here?



John Goerzen wrote:

* We have a working gcc that is a 64-bit executable and generates
64-bit executables.


As far as I can tell, compilers are not self-hosted on pure64 because
we currently seem to be lacking some of the gcc-3.3 build depends.
I found that "blas" (which uses g77) fails to build for me in pure64,
yet there is a binary package in John's archive that is quite usable.
That's what led me to try to rebuild g77 ... and notice the lack.

* My own archive is reaching the limits of its design with about 6000
packages present, and it is hard for others to collaborate.


In the short/medium term, I'm quite happy to have a distributed pool
whereby there are a dozen lines that we all have in our sources.list
so that each line corresponds to one amd64 special interest group.
For example: bootstrap/build, xfree86, kde, scientific, ...

* Latest versions of procps and dpkg-dev are b0rked.


Yeah, what's up with that ? What can we do to help ?

So, where do we go from here? I think the archive situation is
absolutely critical. I am becoming a bottleneck here, and I need to get
myself out of the critical path so that work can continue even if I'm
too busy to grab debs from all and sundry.


How about you maintain a cvs repository on alioth that just holds
your baseline /etc/apt directory's contents. That way, you can easily
recommend adding and removing sources lines and preferences.
Since CVS manages patches, we can retain local modifications too.

Other thoughts are welcome.


My biggest concern is that pure64 is not able to rebuild itself.
You mentioned failing to build a kernel, which is one such problem.
A scripted search, looking only at what I've got installed right now,
found this list of pure64 binary packages where apt-get build-dep
would be unable to satisfy the build dependencies in pure64.

cdbs fails build dependencies
cpp-3.3 fails build dependencies
debian-policy fails build dependencies
dejagnu fails build dependencies
fastjar fails build dependencies
g++-3.3 fails build dependencies
g77-3.3 fails build dependencies
gcc-3.3 fails build dependencies
gcc-3.3-base fails build dependencies
gobjc-3.3 fails build dependencies
kernel-image-2.6.2 fails build dependencies
lib64c6 fails build dependencies
lib64gcc1 fails build dependencies
lib64stdc++5 fails build dependencies
libdb4.1 fails build dependencies
libdps1 fails build dependencies
libg2c0 fails build dependencies
libgcc1 fails build dependencies
libice-dev fails build dependencies
libice6 fails build dependencies
libnewt0.51 fails build dependencies
libobjc1 fails build dependencies
libsasl2 fails build dependencies
libsasl2-dev fails build dependencies
libsasl2-modules fails build dependencies
libsasl2-modules-mysql fails build dependencies
libsm-dev fails build dependencies
libsm6 fails build dependencies
libstdc++5 fails build dependencies
libstdc++5-3.3-dev fails build dependencies
libx11-6 fails build dependencies
libx11-dev fails build dependencies
libxaw7 fails build dependencies
libxext-dev fails build dependencies
libxext6 fails build dependencies
libxft1 fails build dependencies
libxi-dev fails build dependencies
libxi6 fails build dependencies
libxmu-dev fails build dependencies
libxmu6 fails build dependencies
libxmuu-dev fails build dependencies
libxmuu1 fails build dependencies
libxp-dev fails build dependencies
libxp6 fails build dependencies
libxpm-dev fails build dependencies
libxpm4 fails build dependencies
libxrandr-dev fails build dependencies
libxrandr2 fails build dependencies
libxslt1.1 fails build dependencies
libxt-dev fails build dependencies
libxt6 fails build dependencies
libxtrap-dev fails build dependencies
libxtrap6 fails build dependencies
libxtst-dev fails build dependencies
libxtst6 fails build dependencies
libxv-dev fails build dependencies
libxv1 fails build dependencies
lprng fails build dependencies
openoffice.org-mimelnk fails build dependencies
pm-dev fails build dependencies
python-newt fails build dependencies
python-numeric fails build dependencies
python2.1 fails build dependencies
python2.1-dev fails build dependencies
python2.2 fails build dependencies
python2.2-dev fails build dependencies
python2.3 fails build dependencies
python2.3-dev fails build dependencies
python2.3-numeric fails build dependencies
sbuild fails build dependencies
vim fails build dependencies
whiptail fails build dependencies
x-dev fails build dependencies
xbase-clients fails build dependencies
xdm fails build dependencies
xfonts-100dpi fails build dependencies
xfonts-75dpi fails build dependencies
xfonts-base fails build dependencies
xfonts-scalable fails build dependencies
xfree86-common fails build dependencies
xlibmesa-dev fails build dependencies
xlibmesa-gl fails build dependencies
xlibmesa-gl-dev fails build dependencies
xlibmesa-glu fails build dependencies
xlibmesa-glu-dev fails build dependencies
xlibs fails build dependencies
xlibs-data fails build dependencies
xlibs-dev fails build dependencies
xlibs-static-dev fails build dependencies
xserver-common fails build dependencies
xserver-xfree86 fails build dependencies
xterm fails build dependencies
xutils fails build dependencies

Noteworthy items are lib64c6, gcc and libstdc++

I suspect that, when pure64 becomes able to rebuild itself,
the whole porting effort will become much more parallel.

Alex.




Reply to: