hi,

(foreword, this email has nothing to do with bug 653215, but it answers
a post that was CCed there, so I send it there too for completeness).

Il 04/01/2012 10:11, Vincent Cheng ha scritto:
> I would change the b-d on libportmidi-dev from [!kfreebsd-any] to
> [linux-any], given that portmidi also FTBFS on hurd-i386 and I see no
> indication that it's going to be fixed on hurd anytime soon.
Good idea, I did that .
> I've also tried building pygame in a kfreebsd-i386 VM. I have no idea
> how to get the build log out of a VBox VM, so I ended up taking
> screenshots of the log instead; they're attached with this e-mail.
>
I use qemu, here are some suggestions:
- try to scp from the guest to the real host ; with qemu,
  the host is at 10.0.2.1 (or 10.0.2.2 , can't recall for sure)
- setup email and send an email from the guest
- with qemu, while the guest is not running, you can use
  qemu-nbd to mount a qemu disk into the real host

> First problem is that pygame stalls when it can't find some of its
> dependencies (for kfreebsd, this is portmidi and porttime), and
> requires that the user manually types in 'y' at the prompt (otherwise
> the build just seems to stall forever; see pygame_ftbfs1.png).
(it is not stalling forever, it is waiting for input; the problem is
that the output is buffered, so you are not seeing the prompt)
>  How
> will the buildds end up handling this?
In buildds , the input is redirected from dev/null, so by looking in
config_unix.py I can tell that the 'confirm()' call would default to
"no" and the build would be aborted. That is why I patched
config_unix.py , so that it will instead not abort because of a missing
'portmidi' dependency on non linux targets.

> Second problem is that pygame FTBFS on kfreebsd after the user accepts
> the prompt to proceed with the build (see pygame_ftbfs2.png); pygame's
> camera extension is Linux-specific.
>
with the newer pygame it should not; if you have time, please check in
the virtual environment; otherwise we may simply upload it and see if it
works

a.


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to