From: Martin Hejnfelt <mh@newtec.dk>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] splashutils fails to build
Date: Fri, 9 Jan 2015 14:30:03 +0100 [thread overview]
Message-ID: <CAKmi1bWHnjpEpJaosj5oAfYS8B42NfX=gzcSOsgOnjvUBW3GWw@mail.gmail.com> (raw)
In-Reply-To: <CAKmi1bXCo_bYF85=TdOdh2b=bZ3X1pamxddoy4o3BwqfJi7JWA@mail.gmail.com>
2015-01-08 7:46 GMT+01:00 Martin Hejnfelt <mh@newtec.dk>:
> Hi,
>
> After upgrading to OSELAS-Toolchain-2014.12.0, using
> gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16 for
> i686-atom-linux-gnu, suddenly splashutils (of ptxdist-2014.12.0) does
> not build anymore. It fails with this:
>
> CC fbsplashctl-util.o
> CC fbsplashctl-fbsplashctl.o
> CCLD fbsplashctl
> /opt/OSELAS.Toolchain-2014.12.0/i686-atom-linux-gnu/gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized/lib/gcc/i686-atom-linux-gnu/4.9.2/../../../../i686-atom-linux-gnu/bin/ld:
> attempted static link of dynamic object `./.libs/libfbsplashrender.so'
> collect2: error: ld returned 1 exit status
>
> It worked with OSELAS-Toolchain-2013.12.2. so I guess this is an issue
> due to the upgraded compiler tools, however I am no autotools master,
> so I am struggling to iron out why it suddenly refers to the dynamic
> libfbsplashrender.so instead of the static libfbsplashrender.la one...
>
Ok apparently something has changed somewhere so static libraries are
not compiled by default (even though the configure options state them
to be). Thus to get this compiling, I needed to explicitly set
--enable-static in the .make file, and do the same for libpng and
libjpeg (probably also for other libraries that might be needed
depending on the configuration through menuconfig).
Is this a change created by ptxdist, gcc or what?
Thanks :)
Kind regards,
Martin Hejnfelt
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-01-09 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 6:46 Martin Hejnfelt
2015-01-09 13:30 ` Martin Hejnfelt [this message]
2015-01-14 10:31 ` Michael Olbrich
2015-01-14 11:02 ` Martin Hejnfelt
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='CAKmi1bWHnjpEpJaosj5oAfYS8B42NfX=gzcSOsgOnjvUBW3GWw@mail.gmail.com' \
--to=mh@newtec.dk \
--cc=ptxdist@pengutronix.de \
/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