mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Martin Hejnfelt <mh@newtec.dk>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] splashutils fails to build
Date: Wed, 14 Jan 2015 12:02:28 +0100	[thread overview]
Message-ID: <CAKmi1bWE3wVuxwgxxi0sad7pn1euMSBThO6swj3n4_H1FaZdwg@mail.gmail.com> (raw)
In-Reply-To: <20150114103111.GV26436@pengutronix.de>

Hi Michael,

Thank you for clearing this up. So how should this be handled? First
of all, I guess --enable-static should be in the splashutils makefile,
second of all, should libpng and so on, then depend on this in some
way, or can that enable_static=no rule instead be changed directly
from splashutils if needed?

2015-01-14 11:31 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> On Fri, Jan 09, 2015 at 02:30:03PM +0100, Martin Hejnfelt wrote:
>> 2015-01-08 7:46 GMT+01:00 Martin Hejnfelt <mh@newtec.dk>:
>> > 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?
>
> That's a change in PTXdist: We've added enable_static=no to the environment
> (rules/pre/Rules.make). This changes the default --disable-static for all
> configure scripts that have this option.
>
> Michael
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de



-- 
Mvh. / Kind regards
Martin Hejnfelt
Development Engineer

Newtec A/S
Staermosegaardsvej 18
5230 Odense M
Tlf.:+45 66158444
Dir.:+45 63154881

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2015-01-14 11:02 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
2015-01-14 10:31   ` Michael Olbrich
2015-01-14 11:02     ` Martin Hejnfelt [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=CAKmi1bWE3wVuxwgxxi0sad7pn1euMSBThO6swj3n4_H1FaZdwg@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