I think that a clear statement from the kFreeBSD porters about this
would help concluding this debate.
Does anybody have anything to say about this?
I don't think the purpose of your question is concluding the debate, I
think it just tries to enforce your point of view by presenting your
goa
-I/usr/src/kfreebsd-source-8.1/sys/fs/puffs/puffs/../putter -DPUFFSDEBUG
-mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2
-mno-sse3 -ffreestanding -std=iso9899:1999 -c puffs_msgif.c In file
included from @/sys/vnode.h:563,
from puffs_msgif.c:44:
Stop in /us
And while I apologise for the problems we've had with the migration, I'd
like to ask people to just accept some of the changes we've made even
though you think it makes URLs uglier. They're done to avoid cyclic
dependencies between services.
Please note, that not only git links are (have been)
4. Build-Depends - Depends (aka invalid listing in Build-Depends)
http://wiki.debian.org/BerkeleyDB/InvalidBuild-Depends
Packages in list 4 should be fixed because it means either one of:
1. The Build-Depends listing is erroneous (f.e. upstream dropped
support for Berkeley DB)
2. The build p
The webkit #554718 currently on kfreebsd-amd64 blocks building of
seed, yelp, gir-repository, gstreamer0.10 (via gir-repository),
devhelp, kazehakase, ...
For details see
http://lists.debian.org/debian-devel/2009/11/msg00289.html
Petr
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debi
- kFreeBSD:
Debian 6.0 Squeeze should be the first Debian release shipping with
a non-Linux kernel.
Out of curiosity, how is security support working for this and who is
providing it?
The upstream provides their own security advisories, see
http://security.freebsd.org/
http://security
Hello, Debian world!
This is a status update for the Debian GNU/FreeBSD port[1].
Compared to previous status mail [2], this port now consists
of two architectures: kfreebsd-i386 and kfreebsd-amd64.
Currently we focus mainly on kfreebsd-i386.
Status
--
* We have uptodate toolchain and most
Hi.
In fact, there is a successful attempt of package build:
http://experimental.ftbfs.de/build.php?arch=&pkg=openmotif
But only alpha, arm, mips and initial i386 version are already
in unstable, sparc and powerpc are now in incoming.
Regards
Petr
--
To UNSUBSCRIBE, email to [EMAIL
On Wed, 1 Jun 2005, Petr Salinger wrote:
Memory requirement for only these two arrays is roughly 500 MB.
If you have enough RAM + swap (1 GB) it works,
if you have less (512 MB) it fails.
OK, I'm slightly convinced. On the other hand: Isn't this a really strange
error message from ld
9 matches
Mail list logo