Moving the now-"fix released" bug to the qemu-linaro Ubuntu package
** Package changed: findutils (Ubuntu) => qemu-linaro (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/372121
Title:
xargs
This was fixed in qemu in commit:
fd4d81dd04b4e606ce40a41d66368ba77c77c753
long since included in qemu.
** Changed in: findutils (Ubuntu)
Status: Triaged => Fix Released
** Changed in: findutils (Ubuntu)
Assignee: (unassigned) => Riku Voipio (riku-voipio)
--
You received this bug
The example appears to work for me on my setup; that's an Ubuntu
Maverick ARM chroot with qemu 0.12.3 running on an Ubuntu Lucid i386
host (the qemu is newer than Lucid).
sudo chroot /armroot /usr/bin/qemu-arm-static /bin/bash
find /usr -print0 | xargs -0r pwd
/bin/pwd: ignoring non-option argum
** Tags added: arm-porting-queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/372121
Title:
xargs on qemu has bad ARG_MAX
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
** Changed in: findutils (Ubuntu)
Assignee: David Sugar (dyfet) => (unassigned)
--
xargs on qemu has bad ARG_MAX
https://bugs.launchpad.net/bugs/372121
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Loic, we currently do both; we have a default maximum value hard coded,
but we also check at runtime to make sure it is not larger than what
sysconf would allow.
--
xargs on qemu has bad ARG_MAX
https://bugs.launchpad.net/bugs/372121
You received this bug notification because you are a member of
@David Sugar: So we should be computing xargs' max at runtime with
sysconf instead of at build time?
** Changed in: findutils (Ubuntu)
Assignee: (unassigned) => David Sugar (dyfet)
--
xargs on qemu has bad ARG_MAX
https://bugs.launchpad.net/bugs/372121
You received this bug notification bec
The default arg size used in xargs is further checked against the posix
api reported limits. It is possible the upper limit is 128K on
qemu/versatile/arm, but note that whatever value is selected is further
validated against sysconf(_SC_ARG_MAX). However, as noted in sysconf
itself, this does no
I suspect this is not specific to arm, but I'm going to leave it tagged
as armel for the time being since the only machine where you seem to be
able to reproduce it at the moment is qemu-arm. Thanks for your work on
the analysis of the problem.
** Changed in: findutils (Ubuntu)
Importance: Unde
I reported this on #ubuntu-arm (or similar) whilst compiling arm code
for ubuntu/maemo/mer on the open build service; and someone specifically
requested that I tag it 'arm' when I reported it.
The problem only manifests itself using qemu arm emulation ... OTOH I
guess this is fairly important to a
I can't seem to confirm this on my arm system (karmic) nor on my jaunty
x86_64 system. Is there any reason why you believe this may be specific
to arm?
** Changed in: findutils (Ubuntu)
Status: New => Incomplete
--
xargs on qemu has bad ARG_MAX
https://bugs.launchpad.net/bugs/372121
You
** Tags removed: arm
--
xargs on qemu has bad ARG_MAX
https://bugs.launchpad.net/bugs/372121
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listi
actually this still broke... but less often
so I hit it with a bigger stick:
DEFAULT_ARG_SIZE="(64u * 1024u)"
--
xargs on qemu has bad ARG_MAX
https://bugs.launchpad.net/bugs/372121
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
confirmed that reconfiguring xargs with
DEFAULT_ARG_SIZE="(127u * 1024u)"
instead of the default: (128u * 1024u)
fixes the problem.
patch to debian/rules :
--- rules.orig 2009-05-05 15:44:19.0 +
+++ rules 2009-05-05 10:54:23.0 +
@@ -36,7 +36,7 @@
dh_testd
14 matches
Mail list logo
