this:
$ export CODENAME=sid
$ export ARCHES=hurd-i386
$ CONF.sh && ./build.sh
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/CONF.sh b/CONF.sh
index 99e58ad..08ffbd7 100644
--- a/CONF.sh
+++ b/CONF.sh
@@ -62,11 +62,15 @@ export BASEDIR=`pwd`
# export CDNAME=debian
# Bu
itecture as the
> target architecture of the ISO images.
I did not even realise that. So I will add kfreebsd-i386 next.
I expect there might be problems trying to build linux arches from a
kfreebsd host. But we should try to find out, and then maybe fix it.
Regards,
--
Steven Chamberlain
ste...@
when it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
e
idea of what those are; but add to that the kernel and any bootloaders.
Being able to rebootstrap, should be part of the arch release
qualification anyway IMHO.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
esktop environments, tasks, or OpenJDK for example.
Having a stable set of build-essential packages is important for ports
to get DSA-administered buildds, for developers to be able to run it,
and for the port to progress further.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
using devices.tar.gz; even for more exotic use
cases like BSD jails. hurd appears to have something equivalent.
Thanks for letting us know.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Hi,
Paul Wise wrote:
> Do any porters have any input on this page?
> https://wiki.debian.org/GettingPorted
This page seems it will be useful; I will add some bits to it.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
re:
http://buildd.debian-ports.org/status/architecture.php?a=m68k&suite=sid
so it's not clear which are most important, or have the most dependent
packages waiting on them. Is there a better list for anyone who might
want to help with porting?
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
-
I can only find arch:all packages from glibc/2.19-10 in:
http://ftp.debian-ports.org/debian/dists/sid/main/binary-sh4/Packages.bz2
So. although the sh4 buildds have built the sh4 .debs, they're not being
properly installed into that archive; you'll have to ask
debian-ports.org adm
ink of a reason to mail *all* ports that wouldn't be
appropriate for debian-devel-announce; or if your mail only concerns a
few ports it should be convenient to cross-post to the relevant ports'
lists only.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, ema
C 4.9 are
actually okay.
The issue with running the GCC testsuite on kfreebsd-amd64 buildds is
being fixed by FreeBSD upstream, and on Debian buildds within 1-2 weeks.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a
t gcj; or even
gcc-4.8. Was this computed for jessie or sid?
[0]: http://lists.debian.org/5266df9d.9040...@pyro.eu.org
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? C
each
> current port getting a pseudopackage, and the maintainer of the
> pseudopackage being the ports list.
Would that be only for generic issues with a port, not specific to a
package? I doubt this would be used much. These bugs might typically
be reassigned to kernel packages or eglibc anyway.
list, so someone has to
periodically look for and tag things.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/527665af.2040...@pyro.eu.org
rebuild its
toolchain and some essential packages, at least once per week, I think
that would be an accomplishment. And the smaller the initial set of
packages required to boostrap the process, the better.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: OpenPGP digital signature
it ought to be very low. A
working JVM is quite a lot to ask, the current openjdk-7 is not even
built for mipsel in more. mipsel buildds and porterboxes had only 1GB
RAM maximum until now, and that is heavily used already for their
current tasks.
Regards,
--
Steven Chamberlain
ste...@
because the security of the whole system depends on it.
Differences in the output of builds needs to be avoided, or otherwise
explained. It would help greatly if there were frequent builds
happening so we could see unexpected changes occurring.
[2]: https://wiki.debian.org/ReproducibleBuilds
So if
e version (>= 4.8.1-2) whereas m68k still has only the 4.8.0-7 you
uploaded.
You will also first need newer binutils (>= 2.23.52) which is still in
the build queue.
(This applies to ppc64 as well).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to
orts: alpha hppa* m68k powerpcspe ppc64 sh4* sparc64*
* these ports don't appear to have successfully built GCC 4.8 yet.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
Hi Wouter,
Buildd arrakis seems to be down, or at least its status is not being
updated on http://unstable.buildd.net/index-m68k.html
Just checking if you were aware of this?
Also the buildd vivaldi seems to have been idle for a similar duration.
Thanks,
Regards,
--
Steven Chamberlain
ste
20 matches
Mail list logo
