From: Eric Limpens <limpens@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Makefile: change order of libraries to fix linking issue
Date: Wed, 24 Feb 2016 21:55:42 +0100 [thread overview]
Message-ID: <1456347342-3521-1-git-send-email-limpens@gmail.com> (raw)
When building a static variant, link errors occur. Changing the order
of libsndfile and libm fixes this error
Signed-off-by: Eric Limpens <limpens@gmail.com>
---
package/pifmrds/0003-Makefile-fix-static-link-libm.patch | 15 +++++++++++++++
1 file changed, 15 insertions(+)
create mode 100644 package/pifmrds/0003-Makefile-fix-static-link-libm.patch
diff --git a/package/pifmrds/0003-Makefile-fix-static-link-libm.patch b/package/pifmrds/0003-Makefile-fix-static-link-libm.patch
new file mode 100644
index 0000000..eb9cdcf
--- /dev/null
+++ b/package/pifmrds/0003-Makefile-fix-static-link-libm.patch
@@ -0,0 +1,15 @@
+--- pifmrds-0bf57f9ce0d954365a38d8af8e7be6f28521c3f2.orig/src/Makefile 2016-02-24 10:23:41.455695546 +0100
++++ pifmrds-0bf57f9ce0d954365a38d8af8e7be6f28521c3f2/src/Makefile 2016-02-24 10:25:07.003876714 +0100
+@@ -1,10 +1,10 @@
+ CC = gcc
+
+ app: rds.o waveforms.o pi_fm_rds.o fm_mpx.o control_pipe.o
+- $(CC) $(LDFLAGS) -o pi_fm_rds rds.o waveforms.o pi_fm_rds.o fm_mpx.o control_pipe.o -lm -lsndfile
++ $(CC) $(LDFLAGS) -o pi_fm_rds rds.o waveforms.o pi_fm_rds.o fm_mpx.o control_pipe.o -lsndfile -lm
+
+ rds_wav: rds.o waveforms.o rds_wav.o fm_mpx.o
+- $(CC) $(LDFLAGS) -o rds_wav rds_wav.o rds.o waveforms.o fm_mpx.o -lm -lsndfile
++ $(CC) $(LDFLAGS) -o rds_wav rds_wav.o rds.o waveforms.o fm_mpx.o -lsndfile -lm
+
+ rds.o: rds.c waveforms.h
+ $(CC) $(CFLAGS) rds.c
--
1.9.1
next reply other threads:[~2016-02-24 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 20:55 Eric Limpens [this message]
2016-02-24 22:02 ` [Buildroot] [PATCH 1/1] Makefile: change order of libraries to fix linking issue Arnout Vandecappelle
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=1456347342-3521-1-git-send-email-limpens@gmail.com \
--to=limpens@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox