[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#281955: kdepim: FTBFS uses too much space/time to build



On Thu, Nov 18, 2004 at 10:36:14PM -0800, Daniel Schepler wrote:
> Christopher L Cheney <ccheney@debian.org> writes:
> 
> > kdepim now that it uses cdbs and builds static libs takes roughly 3.5x
> > as long to build and 10x the diskspace. This is too much diskspace in
> > fact for it to even to build on s390 and if I did my math right will
> > take somewhere over 200hr to build on m68k. It currently has been
> > building on m68k since Nov 13 05:57:31, about 5.5 days ago.
> >
> > I am still looking into what all contributes to the massive increase in
> > time/space, if you want to discuss this bug in realtime see me on irc.
> 
> I think probably the main issue is that --enable-final mode messes up
> static libraries, so I needed to write a patch to disable that on
> libraries when --enable-static was also passed.  (And previously, I
> just didn't use --enable-final at all because of this.)  Also, the
> plugins all get useless static versions built since libtool can't tell
> when it's building a plugin as opposed to a library.
> 
> I don't see what I can really do about this.  Dropping the static
> libraries entirely would be a policy violation, and compiling static
> libraries which contain just one big .o file wouldn't be much better.

Not using enable-final roughly doubles build time on its on. Also, the
release team has already agreed that not compiling static libraries is
fine as well so it will be ok. None of the other kde packages (or qt
afaik) compile static libraries either due to the massive time/space
increase.

http://lists.debian.org/debian-release/2004/11/msg00145.html
http://lists.debian.org/debian-release/2004/11/msg00148.html

Chris

Attachment: signature.asc
Description: Digital signature


Reply to: