From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Package link issue with Buildroot 2017.02
Date: Wed, 22 Nov 2017 13:50:41 +0100 [thread overview]
Message-ID: <20171122135041.0dd02c44@windsurf.lan> (raw)
In-Reply-To: <884FE859A7028649AB59C40AF813419C0A78DE2900@THSONEA01CMS10P.one.grp>
Hello,
On Wed, 22 Nov 2017 12:08:35 +0100, FOURES Philippe wrote:
> cc LinuxMain.o DriverFuncs.o Config.o ../FtdiAccess.o ../FtdiMilan.o -lrt -lftdi -lstdc++ -L"/home/largo/BR17LTS/buildroot-2017.02.7/output/target/usr/lib" -o AESCDriver
You're building with the host compiler ("cc") but linking with a target
library. This cannot work.
> Ajout du processus fils 0xc28150 (AESCDriver) PID 6073 ? la cha?ne.
> Processus fils actif 0xc28150 (AESCDriver) PID 6073
> /usr/bin/ld : escamotage incompatible /home/largo/BR17LTS/buildroot-2017.02.7/output/target/usr/lib/libftdi.so lors de la recherche de -lftdi
> /usr/bin/ld : ne peut trouver -lftdi
Please use LANG=C when building so that error messages end up being in
english rather than french.
> Attached to the mai,l the makefile
>
>
> Note: this package compilation is working fine with buildroot 2016.02
What is the Buildroot .mk file for this package ? I think it forgets to
pass CC=$(TARGET_CC).
In your Makefile, the lines:
CXXFLAGS += -I"/home/largo/BR17LTS/buildroot-2017.02.7/output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include"
and
LIBS += -L"/home/largo/BR17LTS/buildroot-2017.02.7/output/target/usr/lib"
are wrong. 1/ They are not needed and 2/ They make your package use an
absolute path, which is horrible, because nobody else but you will be
able to build this package.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-11-22 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 11:08 [Buildroot] Package link issue with Buildroot 2017.02 FOURES Philippe
2017-11-22 12:50 ` Thomas Petazzoni [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=20171122135041.0dd02c44@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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.