i.MX28 LTIB build fails with ipsec-tools

[igor-imx]

Hi

Im trying to build a linux image for i.mx28EVM utilizing the latest LTIB L2.6.35_1.1.0_130130

The build fails with ipsec-tools package

Here is the output from LTIB

Processing: ipsec-tools

=========================

Build path taken because: directory build, build key set, no prebuilt rpm,

rpmbuild --dbpath /home/icheifot/WORK/Freescale/i.MX28/ltib/rootfs//var/lib/rpm --target arm --define '_unpackaged_files_terminate_build 0' --define '_target_cpu arm' --define '__strip strip' --define '_topdir /home/icheifot/WORK/Freescale/i.MX28/ltib/rpm' --define '_prefix /usr' --define '_tmppath /home/icheifot/WORK/Freescale/i.MX28/ltib/tmp' --define '_rpmdir /home/icheifot/WORK/Freescale/i.MX28/ltib/rpm/RPMS'  --define '_mandir /usr/share/man' --define '_sysconfdir /etc' --define '_localstatedir /var' -bc --short-circuit  /home/icheifot/WORK/Freescale/i.MX28/ltib/dist/lfs-5.1/ipsec-tools/ipsec-tools.spec

Building target platforms: arm

Building for target arm

Executing(%build): /bin/sh -e /home/icheifot/WORK/Freescale/i.MX28/ltib/tmp/rpm-tmp.46463

+ umask 022

+ cd /home/icheifot/WORK/Freescale/i.MX28/ltib/rpm/BUILD

+ cd ipsec-tools-0.7.1

++ echo arm-none-linux-gnueabi-

++ sed -e 's,-$,,'

+ export X_DIR=arm-none-linux-gnueabi

+ X_DIR=arm-none-linux-gnueabi

++ perl -p -e s,/bin/arm-none-linux-gnueabi-gcc,,

++ which arm-none-linux-gnueabi-gcc

+ export TC_PREFIX=/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-linux-gnueabi

+ TC_PREFIX=/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-linux-gnueabi

+ echo /opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-linux-gnueabi

/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-linux-gnueabi

++ perl -e '

    foreach $path ("$ENV{TC_PREFIX}/$ENV{X_DIR}/include/linux/version.h",

                   "$ENV{TC_PREFIX}/include/linux/version.h",

    "$ENV{TC_PREFIX}/arm-fsl-linux-gnueabi/multi-libs/default/usr/include/linux/version.h",

                   "$ENV{TC_PREFIX}/$ENV{X_DIR}/sysroot/usr/include/linux/version.h",

                   "$ENV{TC_PREFIX}/$ENV{X_DIR}/libc/usr/include/linux/version.h") {

        if(-f $path) {

            warn "found $path";

            $path = @ARGV = ($path);

            last;

        }

    }

    warn("Cannot find version.h\n"), exit(1) unless @ARGV;

    $path = $ARGV[0];

    while(<>) {

        m,UTS_RELEASE\s+"2\.(\d), && do { $lin_series = $1; last };

    }

    if($lin_series eq "4") {

        print "$ENV{DEV_IMAGE}/usr/src/linux/include";

    } else {

        $path =~ s,/linux/version.h,,;

        print $path;

    }

    exit(0);

    '

Cannot find version.h

+ KHDR=

error: Bad exit status from /home/icheifot/WORK/Freescale/i.MX28/ltib/tmp/rpm-tmp.46463 (%build)

RPM build errors:

    Bad exit status from /home/icheifot/WORK/Freescale/i.MX28/ltib/tmp/rpm-tmp.46463 (%build)

Build time for ipsec-tools: 0 seconds

Failed building ipsec-tools

f_buildrpms() returned an error, exiting

traceback:

main:572

Started: Mon Feb 25 17:02:49 2013

Ended:   Mon Feb 25 17:02:50 2013

Elapsed: 1 seconds

These packages failed to build:

ipsec-tools

Build Failed

Exiting on error or interrupt

looks like it can't find the file version.h. how can i fix this issue? Im a complete ltib noobm this is my first try to get it built.

thanks in advance

[OtavioSalvador · Accepted solution]

It seems it depends on kernel to be build before it.

Checking the ipsec-tools recipe in Yocto it depends on kernel to be build, before building the recipe, check:

DESCRIPTION = "IPsec-Tools is a port of KAME's IPsec utilities to the \

Linux-2.6 IPsec implementation."

HOMEPAGE = "http://ipsec-tools.sourceforge.net/"

SECTION = "console/network"

LICENSE = "BSD"

DEPENDS = "virtual/kernel openssl readline flex"

[igor-imx]

Hi Otavio

Thank you very much for the hint.

I will definately try it today.

[OtavioSalvador]

Does it works?

[igor-imx]

Hi Otavio

Im getting another error now, that ltib can't find version.h file.

I think there is a solution i've seen on google in regards to this, however, I'm thinking of focusing completely on yocto distro and use it instead since i keep hearing that freescale will switch to using yocto for all the next releases anyways

thank you for you help

[OtavioSalvador]

Right; yes Yocto looks like a nicer option in my point of view :-)