From: Shawn J. Goff <shawn7400@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding a ModemManager package
Date: Sun, 17 Feb 2013 18:22:53 -0500 [thread overview]
Message-ID: <5121664D.2070207@gmail.com> (raw)
In-Reply-To: <51214BB2.4090907@mind.be>
On 02/17/2013 04:29 PM, Arnout Vandecappelle wrote:
> On 17/02/13 18:07, Shawn J. Goff wrote:
>> I'm trying to add a ModemManager package. While building, I'm getting
>> this error during the installation step: "/usr/lib/libgcc_s.so: file not
>> recognized: File format not recognized". This looks like it's looking at
>> my host's libgcc_s.so instead of the target's version. If that's the
>> case
>> I'm not sure why or how to fix it. I did have to use autogen.sh to
>> create
>> the configure script and lots of other stuff; I did this on my host
>> system, so I'm not sure if that is affecting it.
>
> Hi Shawn,
>
> I haven't been able to reproduce your issue because your patch didn't
> include the libqmi package.
Oops... forgot about that. I've been sitting on that patch because
libqmi v1.0 has some bugs that have been fixed, but they haven't set a
version number since then, so it's just got a sha for the version
number. I'll go ahead and submit that, though.
> However, it is very well possible that the issue is caused by running
> 'autogen.sh'. Is it possible that the libtool patch doesn't get
> applied? I see that libtool adds "-rpath /usr/lib" to the link
> command, and I believe the libtool patch removes exactly that.
>
> To create configure properly, you need to set _AUTORECONF to YES, as
> mentioned by Thomas. Unfortunately, that is not so easy...
>
Yes - I noticed :-)
> - modem-manager uses gettext macros provided by the gettext package,
> so you need to add host-gettext to the dependencies. But host-gettext
> doesn't exist yet - I'll send a patch to add it.
>
Awesome.
> - modem-manager requires gtkdocize to be run. We certainly don't want
> to add gtkdocize to buildroot. But since it just generates two files
> for a total of 350 lines, it's easy to add that with a package patch.
Yes, actually, I do that with libqmi, so I'm familiar with that.
>
> Hopefully this will help you to solve the problem.
>
> Regards,
> Arnout
prev parent reply other threads:[~2013-02-17 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 17:07 [Buildroot] Adding a ModemManager package Shawn J. Goff
2013-02-17 17:31 ` Thomas Petazzoni
2013-02-17 17:56 ` Shawn J. Goff
2013-02-17 18:17 ` Thomas Petazzoni
2013-02-17 21:29 ` Arnout Vandecappelle
2013-02-17 21:35 ` [Buildroot] [PATCH] gettext: add host-gettext Arnout Vandecappelle
2013-02-17 23:22 ` Shawn J. Goff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5121664D.2070207@gmail.com \
--to=shawn7400@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.