Package: freebsd-utils
Version: 6.2-3
Severity: important
Tags: patch
A few scripts from freebsd-utils contain calls that are not
pure bourne/posix shell, namely:
[EMAIL PROTECTED]:~ # fgrep -nr 'exec -a' /bin /sbin
Marco d'Itri dixit:
On May 15, Thorsten Glaser [EMAIL PROTECTED] wrote:
Package: module-init-tools
Version: 6.2-3
Why do I keep receiving bugs for a kfreebsd-i386 package which I do not
maintain?
No idea, in this case I suspect there are two different packages with
the same name. (I thought
Petr Salinger dixit:
Is there any way of determining Debian GNU/kFreeBSD vs Gentoo GNU/kFreeBSD
without using sysctl? I know I can get GNU/kFreeBSD out of uname -o, but how
can I get 'Debian'?
I'm trying to update the bsdstats (http://www.bsdstats.org) script to split
between the two, else
(please Cc me, I'm not on the list, just found it on gmane)
Petr Salinger dixit:
Proper fix would be write sort -u using only /bin a /sbin binaries.
For this task, maybe a uniq-without-sort would be enough. Something like
this (at least works in mksh, maybe it's portable enough for /bin/sh):
Okay, I've found out more about the cause:
sshd is compiled as PIE (position independent executable), but only
Linux, NetBSD and MirBSD can execute them; FreeBSD, OpenBSD and
DragonflyBSD cannot. (The DragonFly gcc ignores -pie because it
knows that its kernel can't execute them anyway.)
So the
Aurelien Jarno dixit:
Thorsten Glaser a C)crit :
Could you give us more details?
Sure, these are however also in the PR.
What problem do you get with this binary?
It's not executable.
Which architecture are you
kfreebsd-i386
And which kernel are you using?
Both 5.4 and 7.0 show the bug
Petr Salinger dixit:
Please, could you try with 6.2 image - kfreebsd-image-6.2-1-686
I will.
Which 7.0 version - 6.99+20060506-0.1 ?
I don't have it in my head right now, but yes, one from 2006,
and I actually wondered about it. (Didn't know the 6.2 is newer;
I just apt-getted that stuff.)
close 430455
thanks
Aurelien Jarno dixit:
An upgrade to a 6.1 kernel may fix the bug.
It did. So the bug is closed for openssh.
How about, we either nuke the 5.4 and 7.0 kernels, or fix them too,
so that no other user will experience this problem?
bye,
//mirabile
--
I believe no one can
Hi Colin,
sorry I didn't know that the close command is deprecated.
As for the PIEs, kFreeBSD 6.x kernel has gained a patch to support
executing PIEs some time ago (since I only tested 5.4 and 7.0 I had
not known that, plus I'm not exactly a heavy Debian user...), and
they backported the fix to
Gianluca Bonetti dixit:
::: NetBSD vs kNetBSD :::
You'll need both. For GNU/kNetBSD, archive qualification and,
eventually, release qualification will be much easier to achieve,
because most of the archive will build unmodified, and the needed
tweaks can be taken from GNU/kFreeBSD. A GNU/NetBSD
Ritesh Raj Sarraf dixit:
I'm running Debian GNU/kFreeBSD but I think ipfw is not shipped in Debian.
The documentation on the port website says to use pf (from obsd).
Hope this helps,
//mirabilos
--
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens
-Spam-Status: No, hits=0.00 required=0.90
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
Thorsten Glaser [EMAIL PROTECTED],
Gonzalo Martinez - Sanjuan Sanchez [EMAIL PROTECTED]
Cc: Edmondas Girkantas [EMAIL PROTECTED]
Date: Mon, 03 Sep 2007 00:16:04
markus schnalke dixit:
So I modified the one from MirBSD
which a) works under Debian GNU/kFreeBSD (I use it there) and b) just
has a Depends: mksh line to be added. (See below.)
I don’t quite like the GNU bash changes ☺
11:16⎜*T* Topic for #gnu-kbsd: http://www.debian.org/ports/kfreebsd-gnu/ |
markus schnalke dixit:
But I found the version for MirBSD by Thorsten Glaser on
http://wiki.debian.org/Debian_GNU/kFreeBSD_FAQ
Wow, I made it into the FAQ. Nice ☺
It does it's job, but only if you comment out the lines 282-307. This
is where the DNS thing is.
When I comment out the lines
Aurelien Jarno dixit:
I don't think so. Do you have an idea why you don't have /dev/tty? If
devfs is mounted, this file should exists.
When I'm logged in via ssh, I have /dev/tty (mksh needs it for full
job control too), but locally or from within GNU screen, I don't.
This is weird.
Hi again,
while they still haven’t brought out an official announcement, this seems
to be better than noting:
│ http://mail-index.netbsd.org/source-changes/2008/04/30/msg005553.html
I also had private replies from Martin Husemann and Alistair Crooks, both
members of the board, confirming this,
Mikael Berthe dixit:
* Thorsten Glaser [EMAIL PROTECTED] [2008-06-29 23:27 +0200]:
Hi!
arc4random(3) is a self-seeding PRNG available on a lot of OSes (all BSDs,
...
Debian with the new libbsd package installed
I wanted to try but there's no such package!
Any progress on the libbsd package
Magnus Holmgren dixit:
What about OpenBSD?
OpenBSD only defines __OpenBSD__ in gcc, therefore you can use
#if defined(__OpenBSD__) !defined(__MirBSD__) to test (as
MirBSD defines both __OpenBSD__ and __MirBSD__ in gcc and pcc).
There’s also sys/param.h which has OpenBSD in OpenBSD but not
in
,v 1.3 2008/04/06 22:35:24
tg Exp $ */
/*-
* Copyright (c) 2007
* Thorsten Glaser [EMAIL PROTECTED]
*
* Provided that these terms and disclaimer and all copyright notices
* are retained or reproduced in an accompanying document, permission
* is granted to deal in this work without
Dixi:
• I also attached the version of arc4random.c currently used by the mksh
package for Debian, SuSE and Fedora/RHEL, as the FreeBSD version which
is currently in libbsd trunk seems to be older
This is the more interesting as the version currently used by you only
exposes part of the
Aurelien Jarno dixit:
Can someone test whether the similar results are also on plain FreeBSD
and other BSDs ?
I have just tried on plain FreeBSD, but I haven't found a way to print
the time with full resolution with the default userspace tools. I guess
the best is to write a small C code, but
Florian Weimer dixit:
I'd also see a change that limits the number of bytes which is read from
/dev/urandom (32 or fewer should be enough). I'm concerned about
looping shell scripts darinign entropy from the pool at an unacceptably
high rate.
For things like that, the OpenBSD and MirBSD kernels
Michael Casadevall dixit:
and in kfreebsd's case, non-feasible as LInux can't currently write to
UFS2 based file systems.
While Linux cannot write to them either, I’d like the installer and the
port in general to handle 4.2FFS (UFS1) as well. For compatibility.
//mirabilos
--
Sometimes they
Thomas Schwinge dixit:
First, the check for gcc_cv_libc_provides_ssp is not complete, as has
already pointed out (with patches!) before, but is still not fixed on
trunk. Let me revisit that: in configure.ac it is being checked for
``case $target in *-*-linux*)'' which should rather match
Thomas Schwinge dixit:
Ideally, IMO, this test (for stack-smashing-protection support in glibc)
should not be done by grepping through SYSROOT's features.h, but instead
by using the CPP for doing that.
Why not just autoconf?
Check for the presence of __stack_smash_handler() in libc… or am I
Joseph S. Myers dixit:
It's desirable to be able to configure GCC correctly in the presence of
installed headers and only a dummy libc.so, so as to get a GCC that can be
used to build the full glibc.
Ah, right, the GNU case. Sorry, I totally did not have that one in mind,
even though I know of
Michael Dexter dixit:
Might anyone have examples of commercial or academic users of Debian
GNU/kFreeBSD? Does it have a killer app?
Porting applications to Debian when you have an allergy to Linux, or
Linux doesn’t work as well on the hardware you use, would be a good
example ☺ On the other
Axel Beckert dixit:
And if I start tcsh, either via ssh -t or from my normal login shell,
I get the following warning:
Warning: no access to tty (No such device).
Thus no job control in this shell.
mksh used to suffer from that too. Upstream patch to access /dev/tty
as well, or just use fd
Package: libc6-dev
Version: 2.9-6
Severity: wishlist
(mass filing with linux-libc-dev and libc6-dev)
/usr/include/aio.h: char __unused[32];
/usr/include/aio.h: char __unused[32];
/usr/include/bits/stat.h:long int __unused[3];
/usr/include/bits/stat.h:long int __unused[3];
Package: linux-libc-dev
Version: 2.6.29-2
Severity: wishlist
(mass filing with linux-libc-dev and libc6-dev)
/usr/include/asm/stat.h:long__unused[3];
/usr/include/linux/icmp.h: __be16 __unused;
/usr/include/linux/sysctl.h:unsigned long __unused[4];
These
Cyril Brulebois dixit:
I guess it could be updated to point to #debian-kbsd on OFTC. (Didn't
know an invitation was required, BTW. WTH?)
Freenode closes channels that way when they move off, by
their policy. A bit brain-dead, but I’ll stick around there
as most people/groups I hang around in are
Debian Bug Tracking System dixit:
Bug#440424: kfreebsd-5 build-depends on gcc-3.4/g++-3.4
Bug#463064: kfreebsd-6: non-standard gcc used for build (gcc-3.4)
Sounds mergeable to me, innit?
//mirabilos
--
[00:02] Vutral gecko: benutzt du emacs ?
[00:03] gecko nö [00:03] gecko nur n
Guillem Jover dixit:
Your version seems to leak the buffer every time it's getting called.
Hm, indeed. Damn. Thanks for pointing this out.
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the number of
seconds between the
Package: libbsd-dev
Version: 0.1.3-1
Severity: important
http://buildd.debian-ports.org/fetch.php?pkg=mksharch=kfreebsd-i386ver=38.1-1stamp=1243464766file=logas=raw
Excerpt from the autoconf-style checks:
... if the compiler works
Dixi quod…
http://buildd.debian-ports.org/fetch.php?pkg=mksharch=kfreebsd-i386ver=38.1-1stamp=1243464766file=logas=raw
Same problem occurs on hurd-i386 but not the other ports
architectures such as m68k.
tags 534019 +pending
thanks
Lucas Nussbaum dixit:
On 21/06/09 at 16:13 +, Thorsten Glaser wrote:
Lucas Nussbaum dixit:
arc4rnd_xs.c: At top level:
arc4rnd_xs.c:167: error: expected ')' before string constant
Could you please try the attached patch? If it works with it,
blame
Petr Salinger dixit:
The #define posix_fadvise(fd, off, len, adv) (-1) is sufficient
for GNU/kFreeBSD build.
But it may not be in the future. Please use autoconf or a similar
mechanism.
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch
Luca Favatella dixit:
This patch adds ufs initrd support.
4.2FFS, UFS2, or both?
I would very much like to be able to install Debian GNU/kFreeBSD on
4.2FFS (aka UFS1) filesystems, not just UFS2.
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the
Nobuhiro Iwamatsu dixit:
I made a patch to support SH.
The patch is bogus, #if defined(FOO) is the correct syntax.
You will probably need to provide either the __LITTLE_ENDIAN__
or __BIG_ENDIAN__ symbol.
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since
Package: wnpp
Severity: wishlist
Owner: Thorsten Glaser t...@mirbsd.de
* Package name: makefs
Version : 20090724
Upstream Author : The MirOS Project miros-disc...@mirbsd.org
* URL : http://www.mirbsd.org/cvs.cgi/src/usr.sbin/makefs/
* License : 4-clause BSD
Luca Favatella dixit:
I'm attaching
* a screenshot of the problem I get in the (monolithic) image built using
makefs
Please attach screenshots in ASCII. I mostly read my eMails either
via ssh or on an 80486DLC laptop from 1993 with not enough RAM for
XFree86®, so I cannot view any images.
How
Luca Favatella dixit:
* a screenshot of the problem I get in the (monolithic) image built
using makefs
Ok, I see now (forwarded to workplace):
I think you really should RTFM. There are quite some options:
-f free-files
Ensure that a minimum of free-files free files (inodes)
On Wed, 5 Aug 2009, Luca Favatella wrote:
It looks like there are no regressions in the produced monolithic and
netboot images.
Cool!
Should I proceed to upload makefs as-is to Debian? Is there someone
here willing to sponsor? Otherwise, Mika Prokop from grml.org has
volunteered to do it if I
Luca Favatella dixit:
Tested. Please see
Great ☺
http://svn.debian.org/viewsvn/d-i/branches/d-i/kfreebsd/installer/build/Makefile?r1=59940r2=59943pathrev=59943
You forgot “diff_format=u” otherwise I see nothing…
Why didn’t you set minfree to 0 from the default of 5% as
it doesn’t make any
Aurelien Jarno dixit:
I will have a look at the package and upload it if everything is fine.
Thanks.
I am a bit concerned by the name though. I understand it comes from the
NetBSD® world, actually. It handles 4.2FFS, UFS2 and ISO 9660 (plus
SUSP, RRIP, El Torito). Support for ext2fs is
Luca Favatella dixit:
Can you please explain me better the difference between -f and
minfree (the man page is not clear). I read:
Sure. -f ensures, for makefs(8), that the filesystem has enough
free inodes, whereas minfree is a tunefs(8) parametre you might
know from ext2fs, which measures the
On Fri, 7 Aug 2009, Aurelien Jarno wrote:
Sorry for the delay, I have finally been able to review your package. It
is basically fine, I have a few minor comments/requests though:
Great!
- I have seen that you are using a CVS repository to maintain the
debian/ directory, and that you have
Petr Salinger dixit:
IMHO, the proper short description should be just fine.
Addressed.
Aurelien Jarno dixit:
In the meanwhile you can live with
the lintian error.
Not changed, (still) waiting for the lintian maintainers' decision
on that. I have, however, looked into the lintian source
Aurelien Jarno dixit:
Not changed, (still) waiting for the lintian maintainers' decision
If you really believe it will be fixed in lintian soon
Now I didn't say *that* ;)
/me notes bugs sitting in the BTS for years
I have just uploaded it.
OK. Luca, good luck, have fun.
//mirabilos, soon to
Aurelien Jarno dixit:
* port of Debian Installer for GNU/kFreeBSD
That is currently on good track
makefs is still hanging in NEW (but I hope not for much longer ;)
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the
Tim Tebbit dixit:
filesystem type unknown partition type 0x83
0x83 is GNU/Linux (originally ext[234]fs, but, contrary to the
specification, also used by e.g. ReiserFS).
You want 0xA5 which is FreeBSD disklabel (bsdlabel), allowed
to contain ufs.
bye,
//mirabilos
--
Hi, does anyone sell
Cyril Brulebois dixit:
| -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -pedantic-errors
| -Werror -Wall -Wfatal-errors -Wwrite-strings -O2 -Wall -O2 -MT
Throw away -pedantic-errors (-pedantic is absolutely counter-productive
nowadays, has been for a couple of years) or -Wfatal-errors,
Rogério Brito dixit:
It can be a good thing to use -ansi -pedantic while compiling
alpha/very rough development versions, so that the compiler keep you on
your place if:
* you're programming by trial-and-error :)
* you're aiming at, say, C89.
* you're not targetting POSIX/SUSv3 OSes but really
Rogério Brito dixit:
Personally, I find the following comment from the FreeBSD ZFS tuning
guide most scary:
Oh please. You don’t have to use it if you don’t want it. But this
doesn’t prevent it from being offered to these who do: “We sell rope
to hang yourself.”
(Someone here mentioned that
Hi,
I filed #550611 (please use libbsd instead of glib for strlcpy)
for netcat-openbsd in the hope to get libbsd’s priority raised
and rid of netcat{-traditional,6}.
Any chances for that? ☺
//mirabilos
--
Yay for having to rewrite other people's Bash scripts because bash
suddenly stopped
jamego1...@andaluciajunta.es dixit:
If the binary blobs of Linux kernel was excluded from main,
Would those blobs in FreeBSD kernel be a DFSG violation?
Depends if it’s a “program” (DFSG #2 – I disagree for firmware that
does *not* run on the host CPU but on, say, a NIC) and whether it
comes
antonandr...@fmi.uni-sofia.bg dixit:
The system is a Virtual Box
VirtualBox does not emulate the i386 platform proper. It is
barely enough to get Windows® and Linux run, and some other
OSes may or may not work (MirBSD for example gets SIGILL or
even SIGSEGV some time in the installation
Axel Beckert dixit:
insserv throws a lot of error messages during the installation of
packages having an init.d script.
apt-get install file-rc…
//mirabilos
--
15:39⎜«mika:#grml» mira|AO: mit XFree86® wär’ das nicht passiert - muhaha
15:48⎜thkoehler:#grml also warum machen die xorg Jungs
Moritz Muehlenhoff dixit:
I suppose this affects Debian/KFreeBSD?
Doesn't GNU eglibc come with its own ld.so?
//mirabilos
--
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the
Hanno Hecker dixit:
modules=`shopt -s nullglob ; cat /etc/modules /etc/modules.d/* \
| sed -e \s/#.*//g\ -e \/^\( \|\t\)*$/d\ `
This is even worse, as ...`.`... (with or without inner
quotes) is always wrong and not portable, however $(...) is guaranteed
by POSIX which then
Luca Favatella dixit:
Is there a way to use d-i to install kfreebsd-i386 from usb?
I don't see any technical reason why not. It probably depends
on the bootloader used.
MirBSD uses the manifold-boot method with MirBSD's loader.
Grml uses the manifold-boot method with GNU GRUB 2.
Others use
Aurelien Jarno dixit:
I have tried that, but it doesn't work. It works fine when used on a
CD-ROM, but not when used on an hard-drive. The grub menu is shown
correctly, but when selecting the install entry, it freezes on
Loading When trying to boot using commands, it also freezes
Steve M. Robbins dixit:
#elif defined(__APPLE__) || defined(__FreeBSD__)
This would work if defined(__FreeBSD_kernel__) too.
return sysctlbyname(hw.ncpu,count,size,NULL,0)?0:count;
Although CTL_HW and HW_NCPU probably would work better,
and you could just include sys/sysctl.h and check
Xavier Grave dixit:
#if defined (__FreeBSD__) || defined (__vxworks) || defined(__rtems__)
Make that:
#if defined(__FreeBSD__) || defined(__FreeBSD_kernel__) || \
defined(__vxworks) || defined(__rtems__)
bye,
//mirabilos
--
Sometimes they [people] care too much: pretty printers [and
Ludovic Brenta dixit:
We were talking about BinMNUs of packages that build-depend on gnat-4.4,
Ok, I understand.
So, I'm still willing to upload a fixed gnat-4.4 if and only if some
other DD is willing to then rebuild all the reverse build-dependencies
and re-upload them. Here is the current
Joachim Wiedorn dixit:
#if defined (__FreeBSD_kernel__) || defined (__FreeBSD__) || defined
(__linux__)
This was the right info for me. And now I see how the strings should
be. Thanks!
Useful trick (at least if you have an installation, VM or porterbox
acces): echo | gcc -E -dD - | less
bye,
Luca Bruno dixit:
You may also want to check http://predef.sourceforge.net/index.php
Heh, I could have needed that for mksh. But then, the site was
still infant back then. Heck, it doesn’t even have entries for
all of mksh’s supported platforms ☺ and some are simply bogus,
for example, Cygwin is
Joachim Wiedorn dixit:
Useful trick (at least if you have an installation, VM or porterbox
acces): echo | gcc -E -dD - | less
Wonderful - that is it! Now I can test this an all other architectures
No.
Only on those where GCC is available (for example, not on DEC ULTRIX),
and then only for
Joachim Wiedorn dixit:
But now I see it is not so easy to test it on other architectures. Does
some now how gcc give the string for 'hurd-i386' architectures? I have
thought it should be simple:
There's the Mach kernel, the Hurd set of translators, the eglibc
and the i386 platform. The Debian
Joachim Wiedorn dixit:
Guillem Jover guil...@debian.org wrote:
As being said on the list, explicitly checking for those on the source
is not usually the correct solution. I've taken a look at the xfe code
Also called imake-style.
But what is the correct solution?
GNU autof^Htools. Benny is
Axel Beckert dixit:
Werner Koch asked me a while ago to submit my Debian GNU/kFreeBSD
talk[1] to the Fr�hjahrsfachgespr�ch (FFG)[2] of the German Unix User
Group (GUUG)[3].
As I will be there anyway, I'll do so.
Of course you can can use my[1] or Tolimar's[5] kFreeBSD slides as base.
Yup.
Russ Allbery dixit:
architectures which are expected to be part of Debian. Debian has
needed to adapt to BSD behavior, non-standard or not, since the project
decided to include the kfreebsd architectures. That's part of porting.
What is wrong with porting kfreebsd behaivour instead?
I
Cristian Ionescu-Idbohrn dixit:
What I have in mind is attached.
Two comments:
* The changes to the comments in libbsd-0.2.0.cii0/Makefile are… weird,
especially in the ifeq case.
* Do not use $(shell ./foo.sh), use $(shell sh foo.sh) instead, which
does not rely on the +x attribute (bad
Nathan Scott dixit:
https://buildd.debian.org/fetch.cgi?pkg=pcp-guiarch=kfreebsd-amd64ver=1.4.7stamp=1276672488file=logas=raw
Heh, this is why mksh’s writing *everything* to stdio…
The configure check that failing does a simple AC_CHECK_LIB
on a library thats clearly been installed OK during
Guillem Jover dixit:
A bit of background info. For GNU/kFreeBSD the kernel images are named
'kfreebsd-image-*', for GNU/Hurd they are named 'gnumach'. (I should
probably rename gnumach to match the current kernel naming convention.)
I wonder if there will ever be packages like
Petr Salinger dixit:
-_SHAREDOPTS= -shared -Wl'-soname $(LIBTARGET)'
+_SHAREDOPTS= -shared -Wl,-soname,$(LIBTARGET)
Yes, this should be pushed upstream, maybe with a pointer
to read the gcc texinfo manual added ;-)
bye,
//mirabilos
--
Support mksh as /bin/sh and RoQA dash NOW!
‣
Archive Administrator dixit:
kfreebsd-8_8.0-8_amd64.changes uploaded successfully to ftp-master.debian.org
kfreebsd-8_8.0-8_amd64.changes uploaded successfully to localhost
WTF? Two mails? -v please…
//mirabilos, still learning the finer points of Debian
--
I believe no one can invent an
Tuco dixit:
by installing with KVM and then converting the disk image. After the
install, everything is working fine in VBox.
This may very well be a Virtualbox issue. The Sun engineers admitted
it's a known bug that it doesn't emulate the i386 platform correctly
and other OSes don't work inside
G�rkan Seng�n dixit:
I agree, please send suggestions on what to do extactly after having
them downloaded. cat them together into manpages.tar.gz, gunzip then
create an orig.tar.gz of that?
Why?
Concatenate them together into the .orig.tar.gz – it’s a tar.gz already
from what I can gather
Aurelien Jarno dixit:
Author: tuco-guest
problem was that GNU realpath() fails for inexistant paths and BSD
realpath() doesn't.
AFAICT, it only doesn't fail if the pathname given may be created,
i.e. if all but the last component exist (and there are no trailing
slashes, per POSIX).
bye,
Torsten Werner dixit:
Interesting. Does someone know how to get the real code from those links?
http://www.freebsd.org/doc/handbook/anoncvs.html
cvs -d anon...@anoncvs1.freebsd.org:/home/ncvs co -PA ports/java/openjdk{6,7}
Gruß
//mirabilos
--
I believe no one can invent an algorithm. One just
Julien Cristau dixit:
On Thu, Oct 21, 2010 at 10:57:08 +0200, Petr Salinger wrote:
ServerArgsLocal=vt7 -br -nolisten tcp
That should be done on linux as well imo.
Yes, why isn’t that default anyway? It is on most systems I know
(although, some don’t use vt7 but 4).
bye,
//mirabilos
--
I
Matthias Klose dixit:
At this point, pretty well after the GCC 4.6.0 release, I would like to avoid
switching more architectures to 4.5, but rather get rid of GCC 4.5 to reduce
maintenance efforts on the debian-gcc side, even before the multiarch changes
Porters side, too. I’m okay with
Guillem Jover dixit:
pkg-config --cflags libbsd-overlay
pkg-config is a GNU abomination and not used by BSD projects.
For existing packages using libbsd-dev (BCCed), several headers will
be removed in the upcoming 0.4.0 upstream release. To test that your
packages will keep building fine, you
Robert Millan dixit:
This patch implements a workaround for __unused name collision with Linux and
Glibc. The trick is to define __unused only when in overlay mode, and then
That won’t help. The overlay mode uses pkg-config which no BSD thing touches.
bye,
//mirabilos
--
Support mksh as
Hector Oron dixit:
Someone more knowledgeable on BSD might know best where headers are broken,
/usr/include/nlist.h is correct.
and which is proper place to fix it.
libbsd broke and should be fixed.
bye,
//mirabilos
--
08:05⎜XTaran:#grml mika: Does grml have an tool to read Apple
⎜
Guillem Jover dixit:
What I've done instead is prepare and send patches to Linux and glibc
upstream, which is the correct fix on this issue IMO:
I’ve sent suggestions like these years ago. Let’s hope
they’ll accept it this time.
Thanks,
//mirabilos
--
“Having a smoking section in a
Robert Millan dixit:
Maybe aiming at EGLIBC would be better?
EGLIBC refused this because it would distance them from GLIBC.
Even when I suggested to run this as ed/sed/perl -pie/whatever
during header installation time.
*sigh*,
//mirabilos
--
22:20⎜asarch The crazy that persists in his
Matthias Klose dixit:
GCC 4.7 is now the default for x86 architectures for all frontends except the D
frontends, including KFreeBSD and the Hurd.
How are the plans for other architectures?
The m68k status (which obviously can’t influence the release decisions)
is as follows: gcc-4.7 builds,
Matthias Klose dixit:
Currently java bindings/packages are built for all architectures, however some
architectures still use gcj as the (only available) Java implementation, and
some OpenJDK zero ports are non-functional at this point, and Debian porters
usually don't care about that. So the
Matthias Klose dixit:
The Java and D frontends now default to 4.8 on all architectures, the Go
frontend stays at 4.7 until 4.8 get the complete Go 1.1 support.
I’d like to have gcj at 4.6 in gcc-defaults for m68k please,
until the 4.8 one stops FTBFSing.
From me nothing against switching C/C++
Steven Chamberlain dixit:
Before that can be changed, I think the gcc-defaults package expects
package version (= 4.8.1-2) whereas m68k still has only the 4.8.0-7 you
uploaded.
Right. That’s because gcj FTBFSes.
You will also first need newer binutils (= 2.23.52) which is still in
the build
Matthias Klose dixit:
I’d like to have gcj at 4.6 in gcc-defaults for m68k please,
until the 4.8 one stops FTBFSing.
please send a patch.
For gcc-defaults? I think that one is trivial…
For gcj? I did not take Compiler Design in what two semesters
of Uni I managed until I ran out of money. I
Steven Chamberlain dixit:
Come to think of it, it must take a day or more for m68k to rebuild
eglibc. This is a more serious problem than resources needed by
Kernel takes a day now (on the fastest VMs), eglibc 3 days,
gcc 5 days (since gcj got folded into it; add another day or
so once gnat
Package: edos-distcheck
Version: 1.4.2-13+b1
Severity: normal
tglase@tglase:~ $ x edos-debcheck -failures -explain
Completing conflicts...* 100.0%
Conflicts and dependencies... * 100.0%
Solving
Package: dose-distcheck
Version: 3.1.3-5
Severity: normal
Hi,
I get the following error with dose-debcheck in both wheezy and sid:
tglase@tglase:~ $ dose-debcheck --deb-native-arch=m68k --failures --explain x;
echo $?
Fatal error in module deb/debcudf.ml:
Unable to get
Niels Thykier dixit:
Then there are more concrete things like ruby's test suite seg. faulting
on ia64 (#593141), ld seg. faulting with --as-needed on ia64
And only statically linked klibc-compiled executables work on IA64,
not dynamically linked ones. I’ve looked into it, but Itanic is so
Don Armstrong dixit:
These are the list of ports that I see:
Question is, where do you see them?
avr32
This one got removed even from debian-ports for several
reasons.
sh
I think there's sh4 but not just sh.
Looking at the buildd pages is probably the best idea.
Combining
John Paul Adrian Glaubitz dixit:
On 11/24/2013 12:47 AM, John David Anglin wrote:
It should be going up now.
So, the buildds are already up and running? Shouldn't they be showing
up on buildd.debian-ports.org [1]?
I think I saw buildd uploads for hppa on incoming.d.o this week.
Paul Wise
Helge Deller dixit:
We noticed, that when we manually binmnu-upload packages, which are
already in the *same version* on debian-ports, then debian-ports ACCEPT
When you binNMU packages you add a +b1, +b2, … suffix to their
versions. ITYM porter upload?
those packages, but if we then try to
1 - 100 of 137 matches
Mail list logo
