Ryan Murray writes:
> A full build log can be found at:
> http://buildd.debian.org/build.php?arch=powerpc&pkg=gcc-4.0&ver=4.0.1-9
>
> /dev/pty* are only used with BSD style ptys. Linux 2.6 has named them
> as CONFIG_LEGACY_PTYS, to be removed at some point. Instead of looking for
> the old /dev/pty*, you should instead attempt to open a pty, and then close it,
> as this will also catch the case where /dev/pty* exists, but the support does
> not exist in the kernel.
>
> You could also look for a mounted /dev/pts filesystem and a valid /dev/ptmx,
> but I think opening a pty with the libC functions is probably best...
well, on m68k, a mounted /dev/pts didn't help. Could you provide such
a test?
Ryan Murray writes: buildd. debian. org/build. php?arch= powerpc& pkg=gcc- 4.0&ver= 4.0.1-9
> A full build log can be found at:
> http://
>
> /dev/pty* are only used with BSD style ptys. Linux 2.6 has named them
> as CONFIG_LEGACY_PTYS, to be removed at some point. Instead of looking for
> the old /dev/pty*, you should instead attempt to open a pty, and then close it,
> as this will also catch the case where /dev/pty* exists, but the support does
> not exist in the kernel.
>
> You could also look for a mounted /dev/pts filesystem and a valid /dev/ptmx,
> but I think opening a pty with the libC functions is probably best...
well, on m68k, a mounted /dev/pts didn't help. Could you provide such
a test?
Matthias