Your message dated Wed, 25 Jun 2008 08:38:19 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#486967: xview: FTBFS: ld: cannot find -lXext
has caused the Debian Bug report #486967,
regarding xview: FTBFS: ld: cannot find -lXext
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
486967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486967
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xview
Version: 3.2p1.4-21.2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080619 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on
i386.
Relevant part:
> gcc -m32 -g -O2 -fno-strict-aliasing -g
> -I/build/user-xview_3.2p1.4-21.2-amd64-jC98_S/xview-3.2p1.4-21.2/build/include
> -I/usr/include -I../../build/include -Dlinux -D__i386__
> -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
> -I/usr/include
> -DX11R6 -Di386 -DNO_CAST_VATOAV -DFUNCPROTO=15 -DNARROWPROTO
> -DOS_HAS_LOCALE -DOS_HAS_MMAP -DDYNAMICLIB
> -DOPENWINHOME_DEFAULT=\"/usr\" -c ol_slider.c -o ol_slider.o
> + rm -f ./xshared/ol_button.o
> + ln -s
> /build/user-xview_3.2p1.4-21.2-amd64-jC98_S/xview-3.2p1.4-21.2/lib/libolgx/shared/ol_button.o
> ./xshared/ol_button.o
> + rm -f ./xshared/ol_color.o
> + ln -s
> /build/user-xview_3.2p1.4-21.2-amd64-jC98_S/xview-3.2p1.4-21.2/lib/libolgx/shared/ol_color.o
> ./xshared/ol_color.o
> + rm -f ./xshared/ol_draw.o
> + ln -s
> /build/user-xview_3.2p1.4-21.2-amd64-jC98_S/xview-3.2p1.4-21.2/lib/libolgx/shared/ol_draw.o
> ./xshared/ol_draw.o
> + rm -f ./xshared/ol_init.o
> + ln -s
> /build/user-xview_3.2p1.4-21.2-amd64-jC98_S/xview-3.2p1.4-21.2/lib/libolgx/shared/ol_init.o
> ./xshared/ol_init.o
> + rm -f ./xshared/ol_misc.o
> + ln -s
> /build/user-xview_3.2p1.4-21.2-amd64-jC98_S/xview-3.2p1.4-21.2/lib/libolgx/shared/ol_misc.o
> ./xshared/ol_misc.o
> + rm -f ./xshared/ol_sb.o
> + ln -s
> /build/user-xview_3.2p1.4-21.2-amd64-jC98_S/xview-3.2p1.4-21.2/lib/libolgx/shared/ol_sb.o
> ./xshared/ol_sb.o
> + rm -f ./xshared/ol_slider.o
> + ln -s
> /build/user-xview_3.2p1.4-21.2-amd64-jC98_S/xview-3.2p1.4-21.2/lib/libolgx/shared/ol_slider.o
> ./xshared/ol_slider.o
> rm -f libolgx.so.3.2.4~
> (cd ./xshared; gcc -m32 -shared -Wl,-soname -Wl,`basename libolgx.so.3.2.4 |
> sed 's/\(\.[0-9]\).*$/\1/'` -o libolgx.so.3.2.4~ ?*.o -lXext -lX11 -lc)
> /usr/bin/ld: cannot find -lXext
> collect2: ld returned 1 exit status
The full build log is available from:
http://people.debian.org/~lucas/logs/2008/06/19
This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3
is now the default on most architectures (even if it's not the case on
i386 yet). Consequently, many failures are caused by the switch to gcc
4.3.
If you determine that this failure is caused by gcc 4.3, feel free to
downgrade this bug to 'important' if your package is only built on i386,
and this bug is specific to gcc 4.3 (i.e the package builds fine with
gcc 4.2).
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
Package: xview
Version: 3.2p1.4-22
I've updated the Build-Depends in latest upload, but forgot to mention it
in the changelog. Thus, I'm closing this bug manually.
--- End Message ---
