gammu: task compile fails with `/oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format`

gammu: task compile fails with `/oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format`

[Paul Menzel]

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

Dear Stanislav,


task compile of `gammu` fails with the following error message using
`angstrom-2010.x` or `minimal-uclibc` for `MACHINE = "beagleboard"`.

        […]
        [ 99%] Building C object python/gammu/CMakeFiles/python_gammu.dir/src/convertors/todo.o
        [ 99%] [ 99%] Building C object gammu/CMakeFiles/gammu.dir/gammu.o
        Building C object python/gammu/CMakeFiles/python_gammu.dir/src/convertors/wap.o
        [ 99%] Building C object gammu/CMakeFiles/gammu.dir/backup.o
        Linking C shared module _gammu.so
        make[3]: Leaving directory `/oe/build-angstrom-next/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/gammu-1.29.0-r0/gammu-1.29.0/build-configure'
        [ 99%] Built target python_gammu
        [100%] Building C object gammu/CMakeFiles/gammu.dir/backupsms.o
        Linking C executable gammu
        /oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format
        collect2: ld returned 1 exit status
        make[3]: *** [gammu/gammu] Error 1
        make[3]: Leaving directory `/oe/build-angstrom-next/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/gammu-1.29.0-r0/gammu-1.29.0/build-configure'
        make[2]: *** [gammu/CMakeFiles/gammu.dir/all] Error 2
        make[2]: Leaving directory `/oe/build-angstrom-next/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/gammu-1.29.0-r0/gammu-1.29.0/build-configure'
        make[1]: *** [all] Error 2
        make[1]: Leaving directory `/oe/build-angstrom-next/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/gammu-1.29.0-r0/gammu-1.29.0/build-configure'
        make: *** [all] Error 2

It would be great if you could fix that.


Thanks,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: gammu: task compile fails with `/oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format`

[Stanislav Brabec]

Paul Menzel wrote:
> Dear Stanislav,
> task compile of `gammu` fails with the following error message using
>         /oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format

Could you try to add curl to DEPENDS and try again (note that you have
to include do_configure call again). Maybe I overseen this dependency.

Well, the recipe contains one ugly FIXME. If somebody would be able to
locate target python includes better, feel free to fix it.

-- 
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus

Re: gammu: task compile fails with `/oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format`

[Paul Menzel]

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

Am Mittwoch, den 01.06.2011, 16:56 +0200 schrieb Stanislav Brabec:
> Paul Menzel wrote:
> > Dear Stanislav,
> > task compile of `gammu` fails with the following error message using
> >         /oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format
> 
> Could you try to add curl to DEPENDS and try again (note that you have
> to include do_configure call again). Maybe I overseen this dependency.

Adding `curl` to `DEPENDS` fixes this issue. It is strange that it is
looking into the stanging area (»File in wrong format«).

I will commit the fix.

> Well, the recipe contains one ugly FIXME. If somebody would be able to
> locate target python includes better, feel free to fix it.

I am just having time for build tests right now. :(


Thanks,

Paul


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: [solved] gammu: task compile fails with `/oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format`

[Paul Menzel]

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

Am Donnerstag, den 02.06.2011, 20:20 +0200 schrieb Paul Menzel:
> Am Mittwoch, den 01.06.2011, 16:56 +0200 schrieb Stanislav Brabec:
> > Paul Menzel wrote:

> > > task compile of `gammu` fails with the following error message using
> > >         /oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format
> > 
> > Could you try to add curl to DEPENDS and try again (note that you have
> > to include do_configure call again). Maybe I overseen this dependency.
> 
> Adding `curl` to `DEPENDS` fixes this issue. It is strange that it is
> looking into the stanging area (»File in wrong format«).
> 
> I will commit the fix.

I committed it in 0fe0f7d5 [1].


Thanks,

Paul


[1] http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=0fe0f7d5629578839192153c012a05a192dc2b41

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: gammu: task compile fails with `/oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format`

[Stanislav Brabec]

Paul Menzel wrote:
> Am Mittwoch, den 01.06.2011, 16:56 +0200 schrieb Stanislav Brabec:
> > Paul Menzel wrote:
> > > Dear Stanislav,
> > > task compile of `gammu` fails with the following error message using
> > >         /oe/build-angstrom-next/angstrom-dev/sysroots/i686-linux/usr/lib/libcurl.so: could not read symbols: File in wrong format
> > 
> > Could you try to add curl to DEPENDS and try again (note that you have
> > to include do_configure call again). Maybe I overseen this dependency.
> 
> Adding `curl` to `DEPENDS` fixes this issue. It is strange that it is
> looking into the stanging area (»File in wrong format«).

It is not strange: Target platform instance of curl was not found but
there was a native curl library in the config path. Attempt to link
against it found a file in wrong format (library for another platform).

See the sysroots/i686-linux part of the path.

-- 
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus