Yocto bug #2639. If a chroot path was long, expanding absolute
paths within the chroot path could overrun a buffer.
Signed-off-by: Peter Seebach
---
meta/recipes-devtools/pseudo/pseudo_1.3.1.bb |8
meta/recipes-devtools/pseudo/pseudo_1.3.bb |8
meta/recipes-devtools
/log/?h=seebs/pseudo
Peter Seebach (1):
pseudo: Update to 1.3.1 (fixing chroot crash)
meta/recipes-devtools/pseudo/pseudo_1.3.1.bb |8
meta/recipes-devtools/pseudo/pseudo_1.3.bb |8
meta/recipes-devtools/pseudo/pseudo_git.bb |6 +++---
3 files changed, 11
:
git://git.yoctoproject.org/poky-contrib seebs/pseudo
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo
Peter Seebach (1):
pseudo: Update to 1.3.1 (fixing chroot crash)
meta/recipes-devtools/pseudo/pseudo_1.3.1.bb |8
meta/recipes-devtools/pseudo
Yocto bug #2639. If a chroot path was long, expanding absolute
paths within the chroot path could overrun a buffer.
Signed-off-by: Peter Seebach
---
meta/recipes-devtools/pseudo/pseudo_1.3.1.bb |8
meta/recipes-devtools/pseudo/pseudo_1.3.bb |8
meta/recipes-devtools
continue to use
the standard debugedit logic in package.bbclass.
Signed-off-by: Peter Seebach
---
meta/classes/package.bbclass |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index e6856cd..1a8c7f8 100644
--- a
inux-yocto/3.0: perf scripting support
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/debugsrc
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/debugsrc
Peter Seebach (1):
package.bbclass: Allow overriding of debugedit starting path
On Wed, 11 Jul 2012 17:12:29 +0100
Richard Purdie wrote:
> I think I at least would find this slightly less confusing as:
>
> workparentdir = d.getVar("DEBUGSRC_OVERRIDE_PATH", True) or
> os.path.dirname(workdir)
Wait, LESS confusing?
I appear to have tragically misunderstood the design goals
On Wed, 11 Jul 2012 18:36:50 +0100
Richard Purdie wrote:
> It should all use 4 space for python functions. There is however a
> twist which is due to the way we handle _prepend and _append. Those
> prepends and appends have whitespace too and I seem to remember
> issues with whitespace matching.
continue to use
the standard debugedit logic in package.bbclass.
Signed-off-by: Peter Seebach
---
meta/classes/package.bbclass |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index e6856cd..f0ca443 100644
--- a
ommit 20405bdab18b7a2b101f818e72863d289d5945e4:
Bruce Ashfield (1):
linux-yocto/3.0: perf scripting support
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/debugsrc
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/debugsrc
Peter Se
20405bdab18b7a2b101f818e72863d289d5945e4:
Bruce Ashfield (1):
linux-yocto/3.0: perf scripting support
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/ppc476
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/ppc476
Peter Seebach (1
A couple of boards use chips which perform noticably better
when optimized for the 476. Add a trivial tune file to let
them run better.
Signed-off-by: Peter Seebach
---
meta/conf/machine/include/tune-ppc476.inc | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
create
project.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo
Peter Seebach (1):
pseudo.inc/pseudo_1.4.bb: update pseudo to 1.4
meta/recipes-devtools/pseudo/pseudo.inc | 12 +---
meta/recipes-devtools/pseudo/pseudo_1.3.1.bb |8
meta/recipes-devtools/pseudo/pseudo_1.4.bb |
This update replaces the half-baked --arch logic with the use
of $CFLAGS to pick compiler flags, on the grounds that it makes
a lot more sense for the build system to pick flags than for
pseudo to try to guess what they should be; this should allow
pseudo to at least compile for targets, and possib
On Thu, 2 Aug 2012 21:08:09 +0100
Richard Purdie wrote:
> Adding seebs to the cc since I suspect he may prefer to merge this
> upstream or he may have feedback?
Ooh, thanks. Yeah, we need to fix this in upstream, but the patch as
provided will likely cause Strange Experiences.
See, if you look
On Thu, 2 Aug 2012 23:00:44 +0300
Andrei Gherzan wrote:
> This is done to avoid "Value too large for defined data type" error
> while trying to remove a file > 2GB.
>
> [Yocto #2881]
I thought "hey, that should be easy" and looked at this for a bit. Then
looked more. Then ran tests. Then looked
On Thu, 2 Aug 2012 17:48:18 -0500
Peter Seebach wrote:
> I think probably the right solution is to use the PSEUDO_STATBUF logic
> that's already in ports, and expand on it a bit.
A followup:
I've got a test version of this tagged PSEUDO_1_4_1. I've got one
report about a c
: fix perl path for target
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/blacklist
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/blacklist
Peter Seebach (2):
base.bbclass: Expand PNBLACKLIST across multilibs too
base.bbclass
The PNBLACKLIST feature does not currently work with multilibs,
because they have different ${PN}. The obvious thing to do is to
do this at the same point that we do the PREFERRED_PROVIDER
and PREFERRED_VERSION fixups. (Making the PNBLACKLIST check
do the for-each-multilib check requires it to do t
The checks for -native/-nativesdk packages, and the iteration over
multilibs, are shared between two (now three) blocks of code, and
nothing ever uses the bare multilib name (instead of the multilib
name plus a hyphen), so restructure this a bit. The checks for
-nativesdk/-native packages are now d
On Fri, 10 Aug 2012 17:57:59 -0500
Peter Seebach wrote:
> The PNBLACKLIST feature does not currently work with multilibs,
> because they have different ${PN}. The obvious thing to do is to
> do this at the same point that we do the PREFERRED_PROVIDER
> and PREFERRED_VERSION fixups.
Got a bug related to this that probably only affects our build
environment, but it caused me to note:
When we're using export/dist as a user-mode NFS root (under pseudo),
the PSEUDO_LOCALSTATEDIR is export/dist/var/pseudo.
This seems a bit weird to me -- I don't think pseudo's db should be
part o
in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/cleanup
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/cleanup
Peter Seebach (1):
base.bbclass: Work even when there's no PNBLACKLIST entries
meta/classes/base.bbclass |2 +-
1 files changed, 1 i
It turns out that the result of getVarFlags is not a list, it's
a dict. So "getVarFlags(...) or []" does not reliably produce
something with a .items. This escaped detection because our
local build environment never ends up running builds without
PNBLACKLIST entries.
Signed-off-by
tory at:
git://git.yoctoproject.org/poky-contrib seebs/varpseudo
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/varpseudo
Peter Seebach (1):
runqemu-export-rootfs and friends: don't put pseudo db in target fs
.../installer/adt-installer/scripts/extract_rootfs |7 +++-
In a few places, we have scripts which use /var/pseudo for
the pseudo state directory controlling a given filesystem. This
seems possibly risky because it means that stuff running under
qemu or whatnot could wipe out the data being used to handle that
rootfs.
Signed-off-by: Peter Seebach
If you have really weird build problems:
Check the pseudo.log file for a given package. A lot of packages are
generating a fair number of diagnostics and warnings some of which
indicate that stuff is non-trivially busted for some packages. A quick
scan of a small build turned up 16 packages with n
On Wed, 22 Aug 2012 09:34:35 -0700
Scott Garman wrote:
> This would mean that if someone tried to put multiple rootfs
> directories in the same subdirectory, they could clobber each other's
> pseudo_state data, correct? Putting multiple rootfs directories in
> the same subdir is a common use case
epository at:
git://git.yoctoproject.org/poky-contrib seebs/varpseudo
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/varpseudo
Peter Seebach (1):
runqemu-export-rootfs and friends: don't put pseudo db in target fs
.../installer/adt-installer/scripts/extract_rootfs |8
$(basename $rootfs)
to avoid problems.
This also solves at least one case (not directly hit by yocto's
tree) wherein you could end up trying to remove a rootfs while
pseudo was using a database inside that rootfs, and thus the
remove would fail.
Signed-off-by: Peter Seebach
---
.../installe
On Wed, 22 Aug 2012 20:47:23 -0500
Peter Seebach wrote:
> +PSEUDO_LOCALSTATEDIR="$pseudo_state_dir
... This quote really IS missing. Something must have gone horribly
wrong with my merge attempt.
-s
--
Listen, get this. Nobody with a good compiler needs to be j
On Wed, 22 Aug 2012 20:39:24 +0100
Richard Purdie wrote:
> I'd wondered about this too. Can you use .pseudo_state to
> make the list sort better and help people with tab completion and so
> on? :)
This is even BETTER. And since my previous submission had a Hilarious
Typo in it, I'll revise with
).pseudo_state
to avoid problems.
This also solves at least one case (not directly hit by yocto's
tree) wherein you could end up trying to remove a rootfs while
pseudo was using a database inside that rootfs, and thus the
remove would fail.
Signed-off-by: Peter Seebach
---
.../installe
git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/varpseudo
Peter Seebach (1):
runqemu-export-rootfs and friends: don't put pseudo db in target fs
.../installer/adt-installer/scripts/extract_rootfs |8
scripts/runqemu-export-rootfs |2 +-
sc
ry at:
git://git.yoctoproject.org/poky-contrib seebs/tmuxfix
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/tmuxfix
Peter Seebach (1):
handle two-word commands with tmux
meta/lib/oe/terminal.py |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
__
Trying to make a devshell using tmux can fail because "tmux new"
expects a single command, not a series of arguments. It does, however,
split strings in a suitable way. So you can quote the command.
The failure mode is particularly arcane, in that you end up
with a message like:
ERROR: Un
On Tue, 11 Jun 2013 10:11:46 -0700
Khem Raj wrote:
> On Jun 11, 2013, at 9:13 AM, Mark Hatle wrote:
>
> >> what happens if you use --disable-libunwind-exceptions
> >
> > As far as I know we have not tried that. Doesn't this change some of the
> > processing though for systems that use unwi
On Wed, 26 Jun 2013 19:05:05 +0200
Erik Botö wrote:
> Yes PSEUDO_UNLOAD=1 should do that, but the hosts libpseudo is not
> found when invoking qemu. Therefore the code in pseudo that would
> clean the environment of any libpseudo.so in LD_PRELOAD before handing
> of to qemu is not run and LD_PREL
On Thu, 11 Jul 2013 15:58:41 +0800
Chunrong Guo wrote:
> *symver.patch causes failure if the host glibc does not provide the
> glibc-2.0 version of the symbol.
I don't think we should take this out unconditionally, because it was added
to address a (different) problem -- we were ending up
On Fri, 12 Jul 2013 02:10:21 +
Guo Chunrong-B40290 wrote:
> Powerpc architecture and ppc64 hosts.
Okay. We haven't previously tried pseudo on those that I know of. We may need
to revisit the way this patch gets applied. For the short term, it might be
possible to apply it only to x86 or x86_
BS is 0, we try the compile for sure, and if it fails,
we've emitted at least some sort of message up near the top of the
compile output that tells you what might be wrong.
Signed-off-by: Peter Seebach
---
meta/recipes-devtools/pseudo/pseudo.inc | 50 +++--
1 fi
The following changes since commit ac5d20f4adac69ea1702694fb50849c9e465b443:
systemd: Remove systemd_unitdir if systemd is not in distro features
(2013-07-23 07:49:54 -0700)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/no32libs
http://git.yoctoproject.org/cgit.cgi/poky-c
This is a followup from some chat in #yocto and elsewhere. To make a
long story short, some of the commercial vendors (like Wind River) tend
to ship prebuilt binaries for glibc, and want to require these binaries
to be used as-is (unless the user has done something special and is
building libc).
On Wed, 25 Apr 2012 20:38:05 -0500
Peter Seebach wrote:
> This is a followup from some chat in #yocto and elsewhere.
Okay, some more followup.
While testing this, I kept burning myself on perfectly reasonable
things to get wrong while defining and using multilibs, so I wrote a
bunch of san
On Thu, 26 Apr 2012 17:01:41 -0500
Mark Hatle wrote:
> split does a whitespace based split automatically, I'm used to
> seeing .split() everywhere. (I won't comment on the other similar
> split items)
Okay.
> > +validities = data.getVarFlags('TUNEVALID') or ""
> "validities"? that a ne
f TARGET_ARCH in SDK_NAME
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/toolchains
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/toolchains
Peter Seebach (2):
tune-sh4.inc: Fix spelling of big-endian feature set
sanity.bbclass: Impl
ndors providing prebuilt toolchain components to
restrict tunings to those based on or compatible with a particular ABI.
Signed-off-by: Peter Seebach
---
meta/classes/sanity.bbclass | 69 ++
meta/conf/documentation.conf |6 ++
meta
In tune-sh3, tune-xscale, and tune-sh4, several FEATURES lines referred
to nonexistent features like "sh3eb" when they should have referred to "sh3
bigendian" or the like. Caught by the TUNEVALID sanity check.
Signed-off-by: Peter Seebach
---
meta/conf/machine/include/tu
anism (which is completely
unused) to allow vendors providing prebuilt toolchain components to
restrict tunings to those based on or compatible with a particular ABI.
Signed-off-by: Peter Seebach
---
meta/classes/sanity.bbclass | 69 ++
meta
On Sat, 28 Apr 2012 16:42:31 -0700
Khem Raj wrote:
> > + valid_tunes = data.getVarFlags('TUNEVALID') or ""
> > + conflicts = data.getVarFlags('TUNECONFLICTS') or ""
> > + split_conflicts = {}
> > + for feature in features:
> > + if feature in conflicts:
> > + if feat
32ac3:
Richard Purdie (1):
qt-4.8.1: Fix compile failures on qemux86
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/toolchains
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/toolchains
Peter Seebach (2):
tune-sh4.inc: Fix spe
ndors providing prebuilt toolchain components to
restrict tunings to those based on or compatible with a particular ABI.
Signed-off-by: Peter Seebach
---
meta/classes/sanity.bbclass | 67 ++
meta/conf/documentation.conf |6 ++
meta
In tune-sh3, tune-xscale, and tune-sh4, several FEATURES lines referred
to nonexistent features like "sh3eb" when they should have referred to "sh3
bigendian" or the like. Caught by the TUNEVALID sanity check.
Signed-off-by: Peter Seebach
---
meta/conf/machine/include/tu
On Mon, 30 Apr 2012 15:42:44 -0500
Mark Hatle wrote:
> Is the above debugging? (I suspect it is) I suggest the following...
Actually, that one's intentional. I originally did it for debugging,
but I thought it was super convenient to actually get a list of the CPU
feature set bitbake thought
On Tue, 1 May 2012 12:25:48 +0200
Koen Kooi wrote:
> TUNE_FEATURES = "armv7a vfp neon cortexa8"
I'd like to suggest a separate patch which uses the TUNEVALID info
to explain these, and also explores the tunings of any selected
multilibs, because this is under-informative in some cases.
-s
-
On Tue, 1 May 2012 11:47:14 +0100
Richard Purdie wrote:
> > This patch also provides a whitelisting mechanism (which is
> > completely unused) to allow vendors providing prebuilt toolchain
> > components to restrict tunings to those based on or compatible with
> > a particular ABI.
^-- this will
c6e08ea6926457:
Saul Wold (1):
eglibc-package: remove /var
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/toolchains
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/toolchains
Peter Seebach (2):
conf/machine: Clean up configuratio
This cleans up and/or corrects a few values from machine includes
for consistency with future toolchain sanity checks, and also adds
the TUNEVALID and TUNECONFLICTS to documentation.conf.
---
meta/conf/documentation.conf |3 +++
meta/conf/machine/include/README
This introduces a sanity check for the toolchain, which verifies
each tuning (including any multilibs), producing meaningful diagnostics
for problems, and also provides some higher-level tuning features.
The TUNEVALID and TUNECONFLICT/TUNECONFLICTS settings were not
implemented. Listed one or two
ebs/poky/meta/conf/layer.conf:7:
# < normal>
# append /home/seebs/poky/meta-yocto/conf/layer.conf:8:
# < normal yocto>
#
# BBFILE_COLLECTIONS= normal yocto
BBFILE_COLLECTIONS="normal yocto"
---
commit fb41e13523dc27c9d4bb9f0232100dd31879c2d5
Author: Peter Seebach
Dat
On Tue, 1 May 2012 21:17:28 +0100
Richard Purdie wrote:
> Ah, I see what's happened here. This variable is used to append to
> BBCLASSEXTEND where there are other values like "nativesdk" and
> "native". Looking at the code, I think you should process
> MULTILIB_VARIANTS.
Ahh, okay.
> Another g
octoproject.org/poky-contrib seebs/toolchains
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/toolchains
Peter Seebach (3):
conf/machine: Clean up configuration values.
sanity.bbclass: Implement initial toolchain sanity checks
sanity.bbclass: Check for bogus values i
This cleans up and/or corrects a few values from machine includes
for consistency with future toolchain sanity checks, and also adds
the TUNEVALID and TUNECONFLICTS to documentation.conf.
Signed-off-by: Peter Seebach
---
meta/conf/documentation.conf |3 +++
meta/conf
on or compatible with a particular ABI.
Signed-off-by: Peter Seebach
---
meta/classes/sanity.bbclass | 73 ++
meta/conf/documentation.conf |6 +++
2 files changed, 79 insertions(+), 0 deletions(-)
diff --git a/meta/classes/sanity.bbclass b/meta/cl
Suggestion that came out of my sanity-checks of multilibs; verify
that stuff in BBCLASSEXTEND is valid.
Signed-off-by: Peter Seebach
---
meta/classes/sanity.bbclass | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/meta/classes/sanity.bbclass b/meta/classes
nf
# /home/seebs/poky/meta-yocto/conf/distro/poky.conf
I am not at all sure that this is done correctly, but it passes obvious
sanity checks.
Would appreciate feedback/comments on these, I plan to clean them
up as pull requests eventually.
commit fee6c6ad07d420565b50fed4216f56b916219c2f
Author: Pet
On Mon, 7 May 2012 16:56:11 -0700
Scott Garman wrote:
> From what I can tell, the =~ regex operator is a bashism. It's also
> one that helps a lot with the code readability. So now that we're
> faced with re-writing the script to avoid using that operator, I'm
> having second thoughts about whet
On Tue, 8 May 2012 14:20:16 -0500
Mark Hatle wrote:
> > BTW: IIRC TUNE_CONFLICTS/TUNECONFLICTS inconsistency was discussed
> > on ML already (I could not find that thread, but still it's used in
> > meta/conf/machine/include/arm
>
> Ya, patches to fix these, and actually check them were sent t
Time for some shell trivia!
Trivia point: PATH=:/usr/bin and PATH=.:/usr/bin are equivalent.
Trivia point: So are PATH=/bin::/usr/bin and PATH=/bin:.:/usr/bin
Trivia point: People love to write stuff like:
PATH=$(THAT_DIRECTORY):$PATH
Trivia point: The shell expands undefined variables to em
On Wed, 9 May 2012 20:49:23 +0100
Richard Purdie wrote:
> I like the patch and I can live with the commit message but could we
> have the right subject line and a signed-off-by please? :)
Heh. I hadn't actually intended this as a pull request, just
commentary, but I can do a proper pull request
in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/cleanup
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/cleanup
Peter Seebach (1):
sanity.bbclass: Detect empty $PATH components too
meta/classes/sanity.bbclass |5 +++--
1 files changed, 3 insert
Empty components in $PATH have the same effect as a . in $PATH,
and are a common side-effect of inserting a misspelled or unset
shell variable in $PATH.
Signed-off-by: Peter Seebach
---
meta/classes/sanity.bbclass |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta
On Wed, 9 May 2012 21:59:49 +0100
Richard Purdie wrote:
> FWIW, this isn't going to work. Its checking the sanity in
> "configuration" space, pre recipe parse so it won't pick up on the
> errors we want it to.
>
> So whilst its well intentioned, it isn't going to work as designed and
> we'll hav
On Wed, 9 May 2012 16:32:17 -0700
Saul Wold wrote:
> >sanity.bbclass: Check for bogus values in BBCLASSEXTEND
> >
> RP commented on this one.
I'm gonna drop that for now, I think. I am looking a little at
per-package sanity checking, but it turns out to be harder than I would
ideally like
On Thu, 10 May 2012 18:13:38 -0500
Mark Hatle wrote:
> + sstate_hardcode_cmd = "sed -e 's:^:%s:g' %s | xargs %s" %
> (sstateinst, fixmefn, sstate_sed_cmd)
How confident are we that the file names can never have whitespace in
them?
-s
--
Listen, get this. Nobody with a good compiler needs
nce commit 36d1717e2ad4ca1620ee9f01b524b5ff2f499b26:
Paul Eggleton (1):
classes/rootfs_*: fix splitting package dependency strings
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/cleanup
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/clea
thing containing
core-image-sato, you don't need to also check for core-image-sato-sdk.
Signed-off-by: Peter Seebach
---
scripts/runqemu | 13 +++--
1 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index 305e46a..fc7363f 100755
---
, rather than keeping modified copies.
Signed-off-by: Peter Seebach
---
meta/conf/distro/include/tcmode-external-csl.inc | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/meta/conf/distro/include/tcmode-external-csl.inc
b/meta/conf/distro/include/tcmode
roject.org/poky-contrib seebs/toolchain
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/toolchain
Peter Seebach (2):
tcmode-external-csl.inc: Allow for overrides
tcmode-external-csl.inc: specify the path you couldn't find
meta/conf/distro/include/tcmode-external
wer: Not enough coffee.)
Signed-off-by: Peter Seebach
---
meta/conf/distro/include/tcmode-external-csl.inc |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/conf/distro/include/tcmode-external-csl.inc
b/meta/conf/distro/include/tcmode-external-csl.inc
index 6bdd466.
There's a few cases where something is a huge list of space-separated
things, and it is desireable to remove one. The example currently
afflicting me is DISTRO_FEATURES_LIBC_DEFAULT; I want to end up with
the distro features including all but one of the words in it.
It seems to me that a counterp
On Tue, 15 May 2012 21:59:15 +0200
Bernhard Reutner-Fischer wrote:
> Really that whole name hardcoding is plain stupid and over-engineered.
> If the darn image exists then, heck, just use it.
This may not be a bad idea, but it's a larger change than I wanted to
make, which is why I didn't change
On Wed, 16 May 2012 07:35:45 +0300
Saul Wold wrote:
> My understanding is that a _subtract is fraught with danger, there
> all sorts of ordering implications.
Yes.
But consider, if you will, the specific case of
DISTRO_FEATURES_LIBC_DEFAULT, and a libc which is just like eglibc
except that it l
en Kooi (1):
Revert "kmod: Use base_libdir for installing libkmod"
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/toolchains
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/toolchains
Peter Seebach (1):
sanity.bbclass:
The tuning changes to sanity.bbclass were almost right, but one of
the messages had a %s with no % operator.
Signed-off-by: Peter Seebach
---
meta/classes/sanity.bbclass |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/classes/sanity.bbclass b/meta/classes
It occurred to me:
In theory, it's a bug if a package is configured such that it does not
actually request hash-style=gnu. In practice, though, the yocto
toolchain is configured so that it's the default.
Maybe there should be a periodic build or two that uses a compiler not
configured that way,
On Thu, 31 May 2012 19:00:04 -0700
Christopher Larson wrote:
> +CSL_MULTILIB_ARGS[i586] = "-msgxx-glibc"
> +CSL_MULTILIB_ARGS[i686] = "-msgxx-glibc"
> +CSL_MULTILIB_ARGS[core2] = "-msgxx-glibc"
> +CSL_MULTILIB_ARGS[x86] = "-msgxx-glibc"
> +CSL_MULTILIB_ARGS[x86-64] = "-msgxx-glibc"
> +CSL_MULTILI
On Thu, 17 May 2012 18:45:58 -0500
Peter Seebach wrote:
> The tuning changes to sanity.bbclass were almost right, but one of
> the messages had a %s with no % operator.
>
> Signed-off-by: Peter Seebach
> ---
> meta/classes/sanity.bbclass |2 +-
> 1 files change
On Sun, 25 Aug 2013 19:40:06 -0500
"Peter A. Bigot" wrote:
> qemu.bbclass adds PSEUDO_UNLOAD=1 in qemu_run_binary to avoid reference to
> pseudo functions that may not exist in the target environment. This patch
> detects the addition of that variable within the environment to which the
> call a
The -symlinks package doesn't really add any value if we're
using update-alternatives. Drop it, leaving a spare RPROVIDES
in case anyone thought they needed it.
Signed-off-by: Peter Seebach
---
meta/recipes-devtools/binutils/binutils.inc |9 ++---
1 files changed, 2 insert
ether
there's a good way to fix that...
The following changes since commit 1149b1fef8912f77d971242dfec151fff5a3aa51:
build-appliance: Update SRCREV for release (2013-10-08 16:33:25 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/binutils-alternatives
http://git.
,
but the determination of whether to list them as alternatives is
being made before the point at which we can easily check for them,
so that can produce warnings.
Signed-off-by: Peter Seebach
---
meta/recipes-devtools/binutils/binutils.inc | 69 +--
1 files changed, 43
On Fri, 18 Oct 2013 16:04:30 +0100
Richard Purdie wrote:
> > -populate_script = "%s/usr/bin/populate-extfs.sh" % native_sysroot
> > +populate_script = "export PSEUDO_PREFIX=%s/usr;" % native_sysroot
> > +populate_script += "export PSEUDO_LOCALSTATEDIR=%s/../pseudo;" %
> >
t;ld.gold" binaries may or may not exist,
but the determination of whether to list them as alternatives is
being made before the point at which we can easily check for them,
so that can produce warnings.
Signed-off-by: Peter Seebach
---
meta/recipes-devtools/binutils/binutils.inc |
ives
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/binutils-alternatives
Peter Seebach (2):
Use alternatives for the binutils-symlinks package.
Drop binutils-symlinks
meta/recipes-devtools/binutils/binutils.inc | 67 ++
The -symlinks package doesn't really add any value if we're
using update-alternatives. Drop it, leaving a spare RPROVIDES
in case anyone thought they needed it.
Signed-off-by: Peter Seebach
---
meta/recipes-devtools/binutils/binutils.inc | 10 ++
1 files changed, 2 insert
On Fri, 18 Oct 2013 22:22:40 -0700
Saul Wold wrote:
> The commit short message needs to be corrected to the binutils: ...
> format please.
Okay. Also, fray points out that I appear to have converted tabs to spaces in
some shell code. I'll try to fix this in the next day or so.
-s
--
Listen, g
On Fri, 18 Oct 2013 22:22:40 -0700
Saul Wold wrote:
> The commit short message needs to be corrected to the binutils: ...
> format please.
Okay, corrected the commit message, also fixed a space/tab issue in the
binutils.inc patch.
-s
--
Listen, get this. Nobody with a good compiler needs to
There were a number of cases where pseudo used plain old stat()
to get dev/inode data for files; on 32-bit hosts, this could fail
if the files were over 2GB, causing pseudo to prevent removing of
large files. This is fixed in 1.4.1.
Signed-off-by: Peter Seebach
---
meta/recipes-devtools/pseudo
ib seebs/pseudo141
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo141
Peter Seebach (1):
pseudo_1.4.1.bb: update to pseudo 1.4.1, fixing 32-bit host problems
meta/recipes-devtools/pseudo/pseudo_1.4.1.bb |8
meta/recipes-devtools/pseudo/pseudo_1.4.bb
1 - 100 of 253 matches
Mail list logo
