This updates to pseudo 1.4.3. Changes:
1. A couple of minor tweaks to reduce difficulties using SDKs built
on slightly more recent machines on older machines; specifically,
avoiding getting @GLIBC_2.7 symbol references for sscanf(), fscanf(),
and open2().
2. Revision of the logic determin
On Fri, 1 Feb 2013 11:29:35 +0100
Martin Jansa wrote:
> Peter can you check this issue:
> http://lists.linuxtogo.org/pipermail/openembedded-core/2013-January/035089.html
> to confirm or disprove that it could be somehow caused by pseudo?
It's possible that the increases in file name length cause
On Fri, 1 Feb 2013 13:22:44 +0100
Martin Jansa wrote:
> You can remove PR when upgrading PV.
Thanks! I had been sort of wondering whether there was a way to get
away from ever-increasing PR, but I hadn't actually followed through to
find out.
-s
--
Listen, get this. Nobody with a good compile
On Thu, Jan 31, 2013 at 04:00:25PM -0600, Peter Seebach wrote:
> This updates to pseudo 1.4.3. Changes:
>
> 1. A couple of minor tweaks to reduce difficulties using SDKs built
>on slightly more recent machines on older machines; specifically,
>avoiding getting @GLIBC_2.7 symbol references
On Thu, Jan 31, 2013 at 04:00:25PM -0600, Peter Seebach wrote:
> This updates to pseudo 1.4.3. Changes:
>
> 1. A couple of minor tweaks to reduce difficulties using SDKs built
>on slightly more recent machines on older machines; specifically,
>avoiding getting @GLIBC_2.7 symbol references
This updates to pseudo 1.4.3. Changes:
1. A couple of minor tweaks to reduce difficulties using SDKs built
on slightly more recent machines on older machines; specifically,
avoiding getting @GLIBC_2.7 symbol references for sscanf(), fscanf(),
and open2().
2. Revision of the logic determin
