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

Re: Bug#644588: gle-graphics: FTBFS(kfreebsd): Message: /usr/lib/libgle-graphics-4.2.2.so: cannot open shared object file: No such file or directory

On Fri, Oct 07, 2011 at 12:08:59PM +0200, Christian T. Steigies wrote:
> On Fri, Oct 07, 2011 at 10:22:32AM +0200, Christoph Egger wrote:
> > Package: src:gle-graphics
> > Version: 4.2.2-5
> > Severity: serious
> > Tags: sid wheezy
> > Justification: fails to build from source (but built successfully in the past)
> > 
> > Hi!
> > 
> > Your package failed to build on the kfreebsd-* buildds:
> I do not understand why it fails now, since it has built before. As you can
> see, the previous binNMU has also failed, while the one before was
> successful:
> https://buildd.debian.org/status/logs.php?pkg=gle-graphics&arch=kfreebsd-amd64
> The problem seems to be that during the build process the binary, that has
> just been built, is run a few times.  It needs a library that has just been
> built and it should use the library from the build directory, since it is
> not installed on the system.  In 4.2.2-4+b1 and -4, the library was found,
> in 4.2.2-4+b2 and -5, the library is not found. What has changed in kfreebsd
> in the meantime, and how do I circumvent it?
I have successfully built 4.2.2-4 (which failed in the last binNMU) and
4.2.2-5 in an unstable chroot on asdfasdf.debian.net, the kfreebsd-amd64
porterbox. On io.debian.net, the kfreebsd-i386 porterbox, the build does not
complete as there is no gs installed in the unstable chroot, but the
executable works where it has failed on your machine:

(sid)cts@io:~/gle-graphics-4.2.2$ ./build/bin/gle -mkinittex                   
GLE 4.2.2[init.tex]-C-R-
If GLE says 'Saving definitions', then compilation was successful.

>> init.tex (686) |end text|
Saving definitions

(sid)cts@io:~/gle-graphics-4.2.2$ ./build/bin/gle gle-refman/title/glelogo.gle 
GLE 4.2.2[gle-refman/title/glelogo.gle]-C-R-[glelogo][.eps]

To me it looks as if your buildd is borken, please try to build
on another machine and close the bug if this is the case.


Reply to: