From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] broken socat
Date: Wed, 03 Aug 2011 09:05:46 +0200 [thread overview]
Message-ID: <4E38F34A.4020407@visionsystems.de> (raw)
In-Reply-To: <CANPyyuOwmztPhQMg876Tvzw2nKqSVzJDDpc0TUkCqdRU2U8uXA@mail.gmail.com>
Am 01.08.2011 23:12, schrieb Mike Williams:
> Has anyone else noticed a broken socat on PPC or other big-endian
> systems? The termios options specified manually in the .mk file appear
> to be wrong, as socat asserts when run because they aren't equal to
> the platform's definition. It appears these options are determined
> during configuration by compiling small programs and testing them, as
> they must be manually set when cross compiling. I know nothing about
> termios, but is it possible that we could just define them based on
> architecture in the .mk file and be done with it?
>
> Additionally, it appears that 2.0.0-b4 has a problem with a UDP-RECV
> source, that 1.7.1.3 does not. Perhaps it would be wise to revert to
> the stable version until the next release is out of beta, along with
> whatever changes fixing the termios problem requires?
Have you reported these issues to socat maintainer?
Yegor
prev parent reply other threads:[~2011-08-03 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 21:12 [Buildroot] broken socat Mike Williams
2011-08-03 7:05 ` Yegor Yefremov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E38F34A.4020407@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.