Timo Mueller [Fri, 8 Feb 2013 15:21:44 +0000 (09:21 -0600)]
documentation: Part 2 of 2 for YP doc integration into Eclipse.
This commit adds the three *.customization.xsl files. I
(Scott Rifenbark). Split the commit because after applying the
18 patches, the list of stuff to stage was huge and I did not
want to add them one-by-one. So I staged them using git add -u.
Here is the general cover letter information from Timo included
with the 18 patches:
-----------------
Hi,
the generation of eclipse help files has been merged from the timo
branch to the master. Since the creation of the timo branch there have
been some changes to the master branch (e.g. new documentation,
renamed documentation).
This patch set does some cleanup for the renamed documentation and
adds eclipse help generation support to the new documentation.
01: Removes the 'the' from the document titles
02..04: Cleanup obsolete artifacts resulting from the merge
05..08: Add eclipse help generation for ref-manual
09..13: Add eclipse help generation for kernel-dev
14..18: Add eclipse help generation for profile-manual
Timo Mueller [Fri, 8 Feb 2013 15:16:33 +0000 (09:16 -0600)]
documentation: Part 1 of 2 updates to integrating docs to Eclipse help.
Hi,
the generation of eclipse help files has been merged from the timo
branch to the master. Since the creation of the timo branch there have
been some changes to the master branch (e.g. new documentation,
renamed documentation).
This patch set does some cleanup for the renamed documentation and
adds eclipse help generation support to the new documentation.
01: Removes the 'the' from the document titles
02..04: Cleanup obsolete artifacts resulting from the merge
05..08: Add eclipse help generation for ref-manual
09..13: Add eclipse help generation for kernel-dev
14..18: Add eclipse help generation for profile-manual
Best regards,
Timo
This patch set originally contained 18 patches. I (Scott Rifenbark)
had to push these changes as two parts. This is the first part.
It does not include creation of the three cusomization files.
Scott Rifenbark [Wed, 6 Feb 2013 20:03:23 +0000 (14:03 -0600)]
adt-manual: Added cross-reference link for Cross-dev toolchain.
I placed a link on the term "Cross-Development Toolchain" in the
section of the same name. This is to help the user see the
recipes related to the toolchain. The link resolves back into
the "Terms" section of the dev-manual.
Scott Rifenbark [Wed, 6 Feb 2013 18:51:39 +0000 (12:51 -0600)]
dev-manual: Updates to expose cross-toolchain recipes.
Added a bulleted list to the "Terms" section to help define
some toolchain recipes such as gcc-cross-initial,
gcc-cross-intermediate, and so forth.
Added a cross-reference link to the term
"Cross-Development Toolchain" in the the "Working Using
Stand-alone Cross-development Toolchains" section.
This gives the reader a way to see more on the toolchain
recipes.
Scott Rifenbark [Tue, 5 Feb 2013 15:31:54 +0000 (09:31 -0600)]
ref-manual: edits to update-alternatives.bbclass description.
Fixes YOCTO #3838
First draft of edits for this class. Removed specific variable
definitions as they are now deprecated. Added a general
explanation of the variable functions. Pointed user to the
commented code in the actual class for details. Removed
statement saying that the build system supports only one
binary per package.
Scott Rifenbark [Mon, 4 Feb 2013 18:56:16 +0000 (12:56 -0600)]
ref-manual: Edits to the question on how source code is fetched.
Updated the question that asks "How doe the OpenEmbedded build
system obtain source code and will it work behind my firewall
or proxy server?". Some of the variables did not have links
or proper font type.
Scott Rifenbark [Mon, 4 Feb 2013 18:34:51 +0000 (12:34 -0600)]
yocto-project-qs: Updates to how to use local directories for source
The section that describes an efficient way to set up the
build system to look in local areas for tarballs needed updated
so that PREMIRRORS was not the focus. The example used does
not even employ PREMIRRORS. So I changed wording to support
the example. I also added a mention of the PREMIRRORS variable
and a linked reference to it for more information.
Scott Rifenbark [Fri, 1 Feb 2013 22:30:12 +0000 (16:30 -0600)]
dev-manual: Various typos fixed
Received a patch from Robert P. J. Day but deleted it from
my Thunderbird account so could not apply it directly.
I applied most of his corrections. A couple I left alone.
Scott Rifenbark [Fri, 1 Feb 2013 22:09:08 +0000 (16:09 -0600)]
dev-manual: Updates to "Using .bbappend Files" section
Fixes YOCTO #3664
Added some information in the note to point out that not all
append files add files into the mix. Some just exist to add
build options. And, in this case the _prepend part of the
FILESEXTRAPATHS statement is not necessary.
Scott Rifenbark [Fri, 1 Feb 2013 21:10:01 +0000 (15:10 -0600)]
dev-manual, ref-manual: Updates for BBPATH.
Two things fixed:
1. A couple examples for setting up a layer.conf file were
using the meta-yocto configuration file as an example.
Turns out this is a bad example because the BBPATH variable
is appended to the LAYERDIR when setting BBPATH rather
than the other way around. That is because meta-yocto
is a distro layer. BSP layers, however, are not distro
layers and are the norm here. So I switched up the way
BBPATH was set and actually called out meta-yocto-bsp
config file as a template.
2. Added a link for the BBPATH variable in the
FILESYSTEM_PERMS_TABLES variable description in the
glossary. Just happened to notice this so I fixed it
Scott Rifenbark [Wed, 30 Jan 2013 21:42:26 +0000 (15:42 -0600)]
ref-manual, dev-manual: Updates to BBMASK variable.
Fixes YOCTO #3662
I added more information to the variable desription in the
glossary for BBMASK. The information included a bit more
syntax information as well as some more complex examples.
I added more reference information to the "Excluding Recipes
From the Build" section to help better describe how the
BBMASK variable works.
Scott Rifenbark [Wed, 30 Jan 2013 20:10:25 +0000 (14:10 -0600)]
ref-manual: Updates to the FILESEXTRAPATHS variable.
Fixed YOCTO #3662
Updates to the description so _prepend is used to add paths
to the front of the search order and use of the variable
without _prepend just adds paths to the end of the
FILESPATH order.
Timo Mueller [Thu, 6 Dec 2012 09:19:53 +0000 (10:19 +0100)]
documentation: Add chunk.quietly option to eclipse processing
The chunk.quietly option disables the output of the docbook
chunker. Creation of a new html file is now longer printed to the
console. This provides a much cleaner output of the eclipse makefile
target.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Thu, 6 Dec 2012 09:19:51 +0000 (10:19 +0100)]
documentation/Makefile: Fix copying of figures folder
When calling the eclipse target twice without calling clean in between
the figures folder was copied as a subfolder of the existing figures
folder. This patch fixes the copy command to correctly copy the
figures folder.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:51 +0000 (09:59 +0100)]
documentation/Makefile: Added conversion of links to other documentation parts.
The script tools/eclipse-help.sed is used to convert links that
point to other documentation parts. This avoids having to leave
the eclipse help center when clicking these links.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:50 +0000 (09:59 +0100)]
documentation/tools/eclipse-help.sed: Processes external links for eclipse html files
The file is used when creating eclipse help html files. It processes
all html files and converts links so that the user can navigate
between different docuementation parts without leaving the eclipse
help center.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:49 +0000 (09:59 +0100)]
documentation/Makefile: logic to make all for yocto-project-qs and cleanup
Eclipse help documents are now created when calling the 'make all'
target on the yocto-project-qs. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:48 +0000 (09:59 +0100)]
documentation/yocto-project-qs/yocto-project-qs.xml: Convert fake-title section into articleinfo
The fake title section is converted into a docbook
article.articleinfo. If used with a custom title page this will lead
to the excapt same output. But I will enable the creation of metadata
from this title information.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:46 +0000 (09:59 +0100)]
documentation/yocto-project-qs/yocto-project-qs-eclipse-customization.xsl: new file
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:45 +0000 (09:59 +0100)]
documentation/yocto-project-qs: Added custom title page
The quick start guide is currently not using a title information to
set the title of the document (e.g. article.title or
article.articleinfo.title).
As other output formats may use the title information to create
metadata this information has to be added to the document. To preserve
current style of the document a custom title page has to be used. With
this for instance 'article.title' can be used instead of the
fake-title section currently used, leaving the style intact.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:44 +0000 (09:59 +0100)]
documentation: Move yocto-project-qs global parameters to customization file
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:43 +0000 (09:59 +0100)]
documentation/Makefile: logic to make all for poky-ref-manual and cleanup
Eclipse help documents are now created when calling the 'make all'
target on the poky-ref-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:40 +0000 (09:59 +0100)]
documentation/poky-ref-manual/poky-ref-manual-eclipse-customization.xsl: new file
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:39 +0000 (09:59 +0100)]
documentation: Move poky-ref-manual global parameters to customization file
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:38 +0000 (09:59 +0100)]
documentation/Makefile: logic to make all for kernel-manual and cleanup
Eclipse help documents are now created when calling the 'make all'
target on the kernel-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:35 +0000 (09:59 +0100)]
documentation/kernel-manual/kernel-manual-eclipse-customization.xsl: new file
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:34 +0000 (09:59 +0100)]
documentation: Move kernel-manual global parameters to customization file
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:33 +0000 (09:59 +0100)]
documentation/Makefile: logic to make all for bsp guide and cleanup
Eclipse help documents are now created when calling the 'make all'
target on the bsp-guide. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:30 +0000 (09:59 +0100)]
documentation/bsp-guide/bsp-guide-eclipse-customization.xsl: new file
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:29 +0000 (09:59 +0100)]
documentation: Move bsp-guide global parameters to customization file
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:28 +0000 (09:59 +0100)]
documentation/Makefile: logic to make all for dev manual and cleanup
Eclipse help documents are now created when calling the 'make all'
target on the dev-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:25 +0000 (09:59 +0100)]
documentation/dev-manual/dev-manual-eclipse-customization.xsl: new file
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:24 +0000 (09:59 +0100)]
documentation: Move dev-manual global parameters to customization file
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:23 +0000 (09:59 +0100)]
documentation/Makefile: logic to make all for adt manual and cleanup
Eclipse help documents are now created when calling the 'make all'
target on the adt-manual. Resulting files are archived into
the tarball as well. When calling 'make clean' artefacts of
the eclipse documentation build are deleted.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:20 +0000 (09:59 +0100)]
documentation/adt-manual/adt-manual-eclipse-customization.xsl: new file
This stylesheet uses the eclipse stylesheets of docbook to create
eclipse help from this documentation. In addition to simple html
files these stylesheets will also create xml files which are
needed to integrate the documentation into eclipse (e.g. toc.xml).
Additional parameters are required so resolve links between different
documentation parts inside eclipse.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:19 +0000 (09:59 +0100)]
documentation: Move adt-manual global parameters to customization file
Standard stylesheet parameters were moved to the docbook customization
file tying them to the docbook stylesheet used. Removing these
parameters simplifies the Makefile.
Furthermore supporting new output formats can now be achieved by
creating a new customization file containing its corresponding
parameters. Parameters that are used across different stylesheets with
different values will then be separated through different
customization files.
Global parameters can still be set through the XSLTOPTS variable since
this precedes the parameters in the customization file.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Timo Mueller [Fri, 30 Nov 2012 08:59:18 +0000 (09:59 +0100)]
documentation/template/titlepage.templates.xml: Remove title info
The title of a pdf document is part of the image used on the title
page. Thus the title defined (e.g. bookinfo.title) in a document
should never be used when creating title pages for pdf documents. As
other output formats may use the title information to create metadata
the title has been removed from the template.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Thu, 14 Feb 2013 11:20:49 +0000 (11:20 +0000)]
mulitilib_header: Avoid sstate checksum issues for -native recipes
The use of arch specific variables like MIPSPKGSFX_ABI was creeping
into the -native sstate checksums of package like ncurses-native.
This is pointless and undesireable. We could add specific variable
exclusions but we might as well just brute force the code to be disabled
in the -native case since we don't use multilibs in the native case.
bitbake: Remove whitelisted vars from non-task deps
Though the value of variables in the BB_BASEHASH_WHITELIST is kept out of the
checksums, dependency on them is not, at least for variables and non-task
functions. In the code, the whitelist is removed from the overall task dep
list, but not the individual variable deps. The result of this is that
functions like sysroot_stage_all and oe_runmake end up with whitelisted
variables like TERM listed in their dependencies, which means that doing
a 'unset TERM' before building will result in all checksums for tasks that
depend on those changing, and shared state reuse not behaving correctly.
This is only really a potential issue for variables from the environment, as
it's the existance/removal of the variable that's an issue, not its value, and
the other whitelisted variables are set in our metadata. This which means in
practical terms the only cases where this is likely to be an issue are in
environments where one of the following are unset: TERM, LOGNAME, HOME, USER,
PWD, SHELL. This may seem like an unlikely circumstance, but is in fact a real
issue for those of us using autobuilders. Jenkins does not set TERM when
executing shell, which means shared state archives produced by your jenkins
server would not be fully reused by an actual user.
Fixed by removing the whitelisted elements from the individual variable deps,
not just the accumulated result.
Richard Purdie [Thu, 14 Feb 2013 10:31:12 +0000 (10:31 +0000)]
bitbake: ConfHandler: Improve regexp to fix mis-parsing of += and no whitespace
If you have:
FOO = "a"
FOO += "b"
FOO+= "c"
The expected result is "a b c" however we were seeing "a b" with the FOO+
variable being assigned the value "c". This isn't the expected result.
We need to make the name part of the variale non-greedy so that any + character
becomes part of the operator. This patch does that. I compared the configuration
in OE-Core before and after the change and only the test case changed.
MiLo [Thu, 14 Feb 2013 07:10:30 +0000 (08:10 +0100)]
Python: Add missing dependency "textutils" to "io" package
Modify the include file and script to generate a missing RDEPENDS.
Install python on target with python-io. Import ssl:
Python 2.7.3 (default, Feb 9 2013, 16:04:35)
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import ssl
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python2.7/ssl.py", line 58, in <module>
ImportError: No module named textwrap
would end up with *both* xxx and xxx2 being added when using a multilib
which is clearly incorrect and undesirable.
The issue is that OVERRIDES has virtclass-multilib-xxxx added to it,
this eventually changed DEFAULTTUNE which then changes
TRANSLATED_TARGET_ARCH which is in OVERRIDES meaning we then need to
re-evaluate the overides and the TRANSLATED_TARGET_ARCH gets applied
twice since once you apply an override, it doesn't get undone.
Expanding DEFAULTTUNE to the correct value in advance avoids the issue
and means only the correct overrides get applied.
Peter Seebach [Wed, 13 Feb 2013 19:43:17 +0000 (19:43 +0000)]
pseudo_1.4.5.bb: Finish fixing linkat()
The 1.4.4 fix replaced possible double-prepending of chroot paths
with possible non-prepending of chroot paths. After significant
evaluation, have settled on a single prepending of the chroot
path as a workable compromise.
Peter Seebach [Tue, 12 Feb 2013 22:52:07 +0000 (16:52 -0600)]
pseudo_git.bb: Bump to pseudo 1.4.4.
The pseudo 1.4.2 linkat() implementation had a broken edge case
in which you could end up with chroot paths being doubled when
using plain link() calls instead of linkat() calls.
Jason Wessel [Tue, 12 Feb 2013 19:36:44 +0000 (13:36 -0600)]
libtool-native_2.4.2.bb: Always use /bin/sed for SED
If you never use sstate and always build everything from scratch you
will never see this problem. However, if you use sstate and build
directories that last a long time eventually you can end up with the
scenario where libtool gets a hard coded path in it for sed, and sed
may not exist. The reason you don't see this problem to often if you
generally build from scratch is that libtool builds before sed and
will pickup the host's /bin/sed.
In my case I used modphp, which doesn't exist in the oe-core. You will
end up with a strange looking error like:
| make[1]: *** [buckets/apr_buckets_alloc.lo] Error 1
| /opt/build/bitbake_build/tmp/sysroots/x86_64-linux/usr/bin/x86_64-linux-libtool: line 981: /opt/build/bitbake_build/tmp/sysroots/x86_64-linux//bin/sed: No such file or directory
The solution is to always use /bin/sed for libtool-native.
Richard Purdie [Wed, 13 Feb 2013 00:16:40 +0000 (00:16 +0000)]
site/x32-linux: Specify double alignment
Double alignment is 8 bytes on x32 but it is defaulting to 4 currently.
This leads to various issues and fontconfig fails to build due to the
mismatch triggering assert failures.
Michael Halstead [Wed, 13 Feb 2013 16:31:03 +0000 (08:31 -0800)]
scripts/qemuimage-testlib: Use wide option to ps calls
Forcing ps to display unlimited column width allows the qemu IP address to
be discovered during sanity testing when the command line is extremely long.
This seems to fix the sanity testing problem on AB05 which was recently updated
to OpenSUSE 12.2. I'm not sure what about qemu or process listing is different
on that distribution but this simpile fix seems to work and my help on other
distro's as well.
Laurentiu Palcu [Tue, 12 Feb 2013 16:12:45 +0000 (18:12 +0200)]
gtk-immodules-cache: add weak asignment for GTKIMMODULES_PACKAGES
This is needed if the GTKIMMODULES_PACKAGES is changed later, in
do_populate_packages for example. This way, we don't have to add another
dumb asignment in the recipe inheriting this.
Laurentiu Palcu [Tue, 12 Feb 2013 16:12:37 +0000 (18:12 +0200)]
image.bbclass: add fall-back functionality when running intercepts
If an intercept script fails, it would be helpful to fall-back to
running the postinstall on target's first boot. In order to achieve
that, the postinstalls that install a host intercept hook will have to
return 1, so that the postinstall is marked as unpacked only. If the
intercept hook fails, then we're ok, the postinstalls will be run on
target anyway. If it succeeds, then mark the packages as installed.
This logic was chosen mainly because of rpm backend which saves the
failed postinstalls in /etc/rpm-postinsts. Hence, in order to mark the
packages as installed, all we have to do is delete the scriptlets from
there.
Laurentiu Palcu [Tue, 12 Feb 2013 16:12:36 +0000 (18:12 +0200)]
Add separate directory for postinstall intercepts
The scripts/postinst-intercepts will contain all postinstall hooks that
we need to run after all packages have been installed.
If one wants to install such a postinst hook, all it needs to do is put
the hook in this directory and, from the package postinstall scriptlet,
call:
postinst_intercept <hook_name> <package_name> <var1=...> ...
This will, practically, add the package_name in the list of packages
that need the hook to run and, also, set any variables that would be
needed in the hook. For example, variables like ${libdir}, ${bindir},
etc. that might depend on distribution can be passed on to the script in
this way.
The upstream_tracking.inc file should keep only the names of the packages
that need to be manually checked for upstream versions by the maintainers.
Removed the packages that were moved into other layers and the ones that
are currently reported by the PRS.
Marko Lindqvist [Mon, 11 Feb 2013 04:02:25 +0000 (06:02 +0200)]
gamin: replace obsolete automake macros with working ones
Add obsolete_automake_macros.patch that replaces automake macros
no longer supported by automake-1.13 with modern constructs.
Removed AM_PROG_CC_STDC. AC_PROG_CC to replace it was already
present.
Marko Lindqvist [Mon, 11 Feb 2013 04:02:02 +0000 (06:02 +0200)]
diffutils: replace obsolete automake macros with working ones
Add obsolete_automake_macros.patch that replaces automake macros
no longer supported by automake-1.13 with modern constructs.
Removed AM_PROG_CC_STDC. AC_PROG_CC to replace it was already
present.
Marko Lindqvist [Mon, 11 Feb 2013 04:01:36 +0000 (06:01 +0200)]
systemtap: replace obsolete automake macros with working ones
Add obsolete_automake_macros.patch that replaces automake macros
no longer supported by automake-1.13 with modern constructs.
Removed AM_PROG_CC_STDC. AC_PROG_CC to replace it was already
present.
Marko Lindqvist [Mon, 11 Feb 2013 04:01:10 +0000 (06:01 +0200)]
libidn: remove help2man dependency
Remove manpage creation. It wasn't working because of help2man
missing when libidn is being built. This attempt to create
manpages without help2man turns from no-op to hard error with
automake-1.13.
Marko Lindqvist [Mon, 11 Feb 2013 04:00:48 +0000 (06:00 +0200)]
texinfo: remove help2man dependency
Remove manpage creation. It wasn't working because of help2man
missing when texinfo is being built. This attempt to create
manpages without help2man turns from no-op to hard error with
automake-1.13.
Apt does not recognize the architecture if a different one is set with
DPKG_ARCH (e.g. armel). This patch writes the correct architecture to
/etc/apt/apt.conf.
Jason Wessel [Tue, 12 Feb 2013 11:08:23 +0000 (05:08 -0600)]
relocate_sdk.py: allow relocate_sdk.py to work with python 2.4.x
Avoid the chicken / egg problem of an SDK that provides a working
python but requires that version of python to extract itself. The
RHEL 5.x systems and some other enterprise Linux systems ship with
python 2.4.x as the default python. We need to at least be able to
extract work executables even if we never use the the host provided
python again.
projects / thirdparty / openembedded / openembedded-core-contrib.git / log
