From: Dirk Vermaak <dirk.vermaak@ntlworld.com>
To: buildroot@busybox.net
Subject: [Buildroot] Difficulties with dynamically linking to libasound.so.2.0.0
Date: Mon, 4 Aug 2008 10:43:35 +0100 [thread overview]
Message-ID: <200808041043.36165.dirk.vermaak@ntlworld.com> (raw)
Hi all,
We are trying to run a program using the libasound.so.2.0.0 shared library on
a sam9260. We have compiled the program on our host machine and it works ok.
We compile for our target and compilation is OK but when we run it we get a
seg fault.
We are pretty sure it is to do with linking to the libasound module as we have
stripped own some code so it only has a couple of printfs in it and this
works ok, but as soon as we add the libasound in the linking we get the seg
fault again.
our complie line is
arm-linux-gcc -Wall -fPIC -D -oramps
DAudio1.1.c -l:libasound.so.2.0.0 -L/home/dirk/diarre/linux/build6/buildroot/project_build_arm/at91sam9260dfc/root/usr/lib
(Sorry about the long paths but we have been trying to eliminate all problems.
Does anyone have any suggestions as to what we are doing wrong here?
Thanks
Dirk.
next reply other threads:[~2008-08-04 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 9:43 Dirk Vermaak [this message]
2008-08-04 10:12 ` [Buildroot] Difficulties with dynamically linking to libasound.so.2.0.0 Hinko Kocevar
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=200808041043.36165.dirk.vermaak@ntlworld.com \
--to=dirk.vermaak@ntlworld.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox