reassign 384575 libafterimage-dev
thanks

On Sat, Aug 26, 2006 at 03:57:19AM +0200, [EMAIL PROTECTED] wrote:

> Bastian Blank <[EMAIL PROTECTED]> writes:

> > Package: aterm
> > Version: 1.0.0-3
> > Severity: serious

> > There was an error while trying to autobuild your package:

> >> Automatic build of aterm_1.0.0-3 on debian-31 by sbuild/s390 85
> > [...]
> >> ** Using build dependencies supplied by package:
> >> Build-Depends: dpatch (>= 2.0.9), debhelper (>= 4), libx11-dev, libxt-dev, 
> >> libafterimage-dev
> > [...]
> >> gcc -rdynamic -o aterm command.o graphics.o grkelot.o main.o menubar.o 
> >> misc.o netdisp.o rmemset.o screen.o scrollbar.o utmp.o xdefaults.o 
> >> pixmap.o thai.o   -lAfterImage -lAfterBase -lfreetype -lz -ltiff -lX11 
> >> -lSM -lICE -lXext -ljpeg -lpng -lungif -lz -lm     -lX11  
> >> /usr/bin/ld: cannot find -lfreetype
> >> collect2: ld returned 1 exit status
> >> make[2]: *** [aterm] Error 1

> It looks to me like the above libraries aren't necessary for aterm to
> build, but `afterimage-config --libs` thinks they are. I can build
> aterm with just -lAfterImage -lAfterBase.

> Therefore I suggest that afterimage-config be fixed to not pull in the
> unnecessary libraries like that. Does that seem reasonable? Meanwhile,
> if afterimage-config hasn't been fixed in a week, I'll upload an aterm
> package with a temporary workaround.

Please don't.  One way or another, the bug needs to be fixed in
libafterimage-dev (either fixing the output of afterimage-config, or adding
dependencies to libafterimage-dev); adding workarounds to aterm is only
likely to cause more bugs farther down the line.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to