| Age | Commit message (Collapse) | Author | Files |
|---|
|
to take into account the new staging location of perl. This will also force
a rebuild of libxml-parser-perl which should now work.
|
|
properly terminating a quote. This is in theory the fix for the /bin/sh ->
/bin/dash problems with perl, however since I don't have any issues here with
dash (ubuntu 6.10) I can't confirm this. The patch is an obvious fix though
so I'm adding it.
|
|
environment and use that instead of the configured location of PERL_INC.
Without this PERL_INC for non-native recipes ends up pointing at where the
headers will be located on the target. In theory we could override this in
cpan class when calling build.PL but for some packages, such as
libxml-parser-perl, that only fixes the top-level makefile and is not
propagated to the sub-makefiles. This change results in MakeMaker always
picking up the correct staged location of the include files without
effecting where they expect to be found on the target.
|
|
perl-native to remove the various directories and to remove the host
specific path components. This is to make it easier to refer to the staged
perl location from other places, such as when trying to tell things where
the perl include files are located.
|
|
else happens to want to use them.
|
|
been effected by the revent CFLAGS changes to perl 5.8.8.
|
|
the CFLAGS from the perl configuration with the OE CFLAGS we prepend the OE
CFLAGS. This is needed to ensure that compiler defines (such as _GNU_SOURCE)
are correctly definied when building perl modules. This primarily effects
modules that link against the core perl library, such as libxml-parser-perl.
|
|
|
|
with the new version of perl.
|
|
Some distributions have already started to use this so it's probably about
time to promote it to the default.
|
|
cause issues with upgrading from earlier 5.8.8 versions (perl-lib will
remain instead of upgrading to libperl5) but it'll actually make upgrades
from 5.8.7 work. I can't see how to fix the 5.8.8 upgrading easily. The
renaming was disabled due to a mistake on my part.
|
|
perl builds on some hosts.
|
|
perl-native configure script was added -I/usr/include/gdbm to the ccflags if
you host had a /usr/include/gdbm/ndbm.h header, even though gdbm support is
disabled. This patch stops the configure script adding that even if it finds
the header there.
|
|
cpan-base.bbclass, and then update the cpan modules to no longer manually
specify this. Also remove references to the new removed .packlist files.
|
|
from being installed. Since we use perl-native to do the cpan module
installs we need to changed perl-native as well to stop cpan modules from
getting .packlist files. This is a new patch since just the .packlist
related part has been extracted from the larger patch.
|
|
from the configure task in perl to the stage task in perl-native where it
belongs - perl shouldn't be messing with the staged perl-native.
|
|
cpan.bbclass changes.
|
|
the PACKAGES_DYNAMIC declaration for the perl modules. This declaration
appears to be global though - so if either of the older perl versions exist
it actually works - bitbake picks up the definition from the older recipes
even though it isn't building them. This shows up as "No providers of
runtime build target <x>" errors where x is a perl module. Thanks to Koen
for figuring this one out.
|
|
This is done by allowing gcc to search for errno.h by itself instead
of manually searching for. The manual search was looking in
STAGING_INCDIR and that's not where the external toolchains headers
are. This whole test is really for handle other compilers and
operating systems, so the simple make gcc do itself should be fine
for us. Closes #1700.
|
|
needed for perl since it doesn't run makedepend.SH. Closes #2168
|
|
appropriate libarary and include directories for exapt to the
makefile.
NOTE: This still doesn't work since it tries to use the host headers
when linking to perl. Fixing this properly will need "perl" to be
installed in the staging area (currently we stage perl-native only).
|
|
* Modify perl to install a copy of it's configuration during staging. This
will allow us to get at the perl settings for the target when building
cpan modules.
* Modify perl-native to allow selection of the host or target configuration
based on an environment variable. This will allow the cpan class to select
the appropriate configuration based on if we are building the native
package or not.
* Modify cpan.bbclass to set the environment variable to an appropriate
value to tell perl native to select the appropriate settings based on if
we are building native or target modules.
This change fixes some modules that were compiled for the host instead of
the target (libversion-perl for example) and fixes up some of cpan modules
that include additional subdirectories with their own makefiles.
|
|
files for perl modules built using cpan will end up in different places
depending on which version of perl they are being built with. Modules that
explicitly set various FILES_ values were using the paths that are only
valid for the older versions of perl. Calculate and set the correct path in
cpan.bbclass and use that in the FILES_ variables so that it'll be correct
for all versions of perl.
|
|
|
|
* don't install packlists - we don't need them and it saves space (debian
patch)
* don't split POSIX module over perl and perl-arch dirs (debian patch)
* add a -doc package and put all the random documentation and examples from
the perl tree in it.
* include all the .pod's from over the tree in the .pod package
* include the .e2x files in the encode package
|
|
match the debian configuration. It moves these configuration files to /etc/
to allow for read only /usr installations.
|
|
dependency file itself to make the main recipe a bit more readable. Also
move the two dependencies that were manually added to the the dependenecy
list file and fix use RDEPENDS instead of DEPENDS.
|
|
installed on the target with those that are suitable for the target. This
has no effect on actually using perl but would have an effect on trying to
build perl modules on the target.
|
|
style FHS compliant layout rather then OE specific layout that was being
used previously. Note that cpan perl modules build under OE won't work with
this because they expect the 5.8.7 type layout (this will be fixed later.)
|
|
common file to make it easier to edit the common settings. A few settings
were changed to help make the configurations closer.
|
|
.inc file and include it in the two recipes that need the list.
|
|
testing is done.
Main differences from the 5.8.7 recipe are:
* Always use gcc to link. Same arch's require this, while others can
happily use ld. Use gcc for everything.
* Fix threading issues by enabling threading in both perl-native and
perl. In fact make the configurations almost identical.
* No per ARCH configuration, just 32/64/le/be configs. This should
stop configurations differing between arch's which made fixing
things 5.8.7 difficult. Also means new ARCH's should work without
any changes.
* Fix up the way miniperl is handled so it shouldn't be the cause of
problems for people anymore.
* Stop perl-modules depending on perl-dbg, perl-pod, perl-dev etc.
* In theory should work for MACHINE="native" now.
Only tested for an sh4/glibc target built on an x86_64 host so far. A
lot more testing and more cleanups are needed before this is ready to
be enabled by default. NOTE: You must build the matching version of
perl-native before attempting to build perl (that applies for any
version).
|
|
build perl
|
|
only really useful for this version of perl the way it's written.
|
|
using PIC for compiling shared libraries.
|
|
patches out of the common directory and only specify common files in
the SRC_URI in perl.inc, move the others to the version specific
.bb's.
|
|
wiping out the options that were set for sh3/sh4 - we only need to init the
OPTIONS once.
|
|
|
|
targets.
Thanks to Jamie Lenahan for the help
|
|
configures and compiles, but still doesn't install.
|
|
|
|
for powerpc targets
|
|
|
|
|
|
it.
|
|
mailing list. There should be no functionality changes yet.
|
|
|
|
names the actual module instead of using python. Should help with the
current parse errors that is apparently occurring with new versions of
bitbake. The python version was helpful when messing with lots of these
things but serves no purpose now.
|
|
|
|
|
