Bug#455041: Symlinks to libgcjwebplugin.so are not created automatically after clean install
Package: java-gcj-compat-plugin Version: 1.0.76-5 Severity: normal After installation of the java-gcj-compat-plugin package, the applets still did not work in Iceweasel (instead, "Plugins required" message kept popping up), until I manually created a link to the plugin file in the browser's plugins directory: ln -s /usr/lib/jvm/java-1.5.0-gcj-4.2-1.5.0.0/jre/lib/libgcjwebplugin.so /usr/lib/iceweasel/plugins/libgcjwebplugin.so The install or configure script did not do this automatically. Neither for Iceweasel, nor for any of the other supported browsers. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.22-2-amd64 Debian Release: lenny/sid 500 testing apt-proxy.i 500 stable apt-proxy.i --- Package information. --- Depends (Version) | Installed ==-+-= java-gcj-compat (= 1.0.76-5) | 1.0.76-5 gappletviewer-4.2 | 4.2.1-5 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#453267: tested patch
On Wed, 05 Dec 2007, Neil Williams wrote:
> Raphael Hertzog wrote:
> > On Tue, 04 Dec 2007, Neil Williams wrote:
> >> On Wed, 5 Dec 2007 00:01:22 +0100
> >> Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> >>
> >>> On Tue, 04 Dec 2007, Neil Williams wrote:
> +my @shlibdeps=();
> +# ARCH for some awkward builds
> +my $crossprefix = Dpkg::Arch::debarch_to_gnutriplet($ENV{ARCH}) if
> ($ENV{ARCH});
> >>> What's the role of $ARCH ? And why shall we consider that we're
> >>> crossbuilding only because this variable is set ?
> >> Not cross building - building a cross compiler.
> >
> > Do we need to check twice for building a cross-compiler ? We don't need to
> > check $ARCH if we already have DEB_TARGET_GNU_TYPE != DEB_BUILD_GNU_TYPE,
> > no ?
>
> My first patch did exactly that - and failed on building a cross
> compiler. gcc needs dpkg-shlibdeps to take notice of $ARCH in the
> preparation of libgcc1-$arch-cross and other libraries used in the
> complete toolchain. It needs (and sets) DEB_TARGET_GNU_TYPE !=
> DEB_BUILD_GNU_TYPE at other stages of the build.
If that's the case, I'd like to know if this is deliberate and really
required... can't the gcc package be consistent and always have both
DEB_TARGET_GNU_TYPE and DEB_BUILD_GNU_TYPE properly set ?
(Ccing [EMAIL PROTECTED] to have their opinion)
Cheers,
--
Raphaël Hertzog
Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#453267: tested patch
Raphael Hertzog wrote: > On Wed, 05 Dec 2007, Neil Williams wrote: >> My first patch did exactly that - and failed on building a cross >> compiler. gcc needs dpkg-shlibdeps to take notice of $ARCH in the >> preparation of libgcc1-$arch-cross and other libraries used in the >> complete toolchain. It needs (and sets) DEB_TARGET_GNU_TYPE != >> DEB_BUILD_GNU_TYPE at other stages of the build. > > If that's the case, I'd like to know if this is deliberate and really > required... can't the gcc package be consistent and always have both > DEB_TARGET_GNU_TYPE and DEB_BUILD_GNU_TYPE properly set ? Even if gcc changes that behaviour in 4.2 (or 4.3), lots of people still need to be able to build cross compilers from older versions of gcc, especially 4.1 and some even need 3.3 or 3.4. Emdebian still hosts 4.1 and 3.4 toolchains: http://www.emdebian.org/toolchains/search.php?package=gcc-3.4-arm-linux-gnu It's not sensible to say that these cannot be built in the future without writing a whole new diversion for dpkg-shlibdeps. Emdebian and lots of other people doing cross building need backwards compatibility here. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ signature.asc Description: OpenPGP digital signature
Processed: [bts-link] source package gnat-4.1
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gnat-4.1 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #246186 > # * http://gcc.gnu.org/PR15799 > # * remote status changed: WAITING -> NEW > usertags 246186 - status-WAITING Bug#246186: gnat: Legal program rejected, using Boolean'Base Usertags were: status-WAITING. Usertags are now: . > usertags 246186 + status-NEW Bug#246186: gnat: Legal program rejected, using Boolean'Base There were no usertags set. Usertags are now: status-NEW. > # remote status report for #246387 > # * http://gcc.gnu.org/PR15805 > # * remote status changed: ASSIGNED -> RESOLVED > # * remote resolution changed: (?) -> FIXED > usertags 246387 - status-ASSIGNED Bug#246387: [Fixed in 4.3] Illegal program not detected, allows writing through access to constant Usertags were: status-ASSIGNED. Usertags are now: . > usertags 246387 + status-RESOLVED resolution-FIXED Bug#246387: [Fixed in 4.3] Illegal program not detected, allows writing through access to constant There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #306834 > # * http://gcc.gnu.org/PR21489 > # * remote status changed: ASSIGNED -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 306834 + fixed-upstream Bug#306834: gnat: Wrong code generated for legal program, RM 6.4.1(13), 9.5.1(3), 9.5.3(8) Tags were: upstream Tags added: fixed-upstream > usertags 306834 - status-ASSIGNED Bug#306834: gnat: Wrong code generated for legal program, RM 6.4.1(13), 9.5.1(3), 9.5.3(8) Usertags were: status-ASSIGNED. Usertags are now: . > usertags 306834 + status-RESOLVED resolution-FIXED Bug#306834: gnat: Wrong code generated for legal program, RM 6.4.1(13), 9.5.1(3), 9.5.3(8) There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #408703 > # * http://gcc.gnu.org/PR30618 > # * remote status changed: UNCONFIRMED -> RESOLVED > # * remote resolution changed: (?) -> FIXED > usertags 408703 - status-UNCONFIRMED Bug#408703: [Fixed in 4.3] Compilation hangs: infinite loop in sem_ch8.end_use_clauses Usertags were: status-UNCONFIRMED. Usertags are now: . > usertags 408703 + status-RESOLVED resolution-FIXED Bug#408703: [Fixed in 4.3] Compilation hangs: infinite loop in sem_ch8.end_use_clauses There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #429934 > # * http://gcc.gnu.org/PR32452 > # * remote status changed: UNCONFIRMED -> RESOLVED > # * remote resolution changed: (?) -> FIXED > usertags 429934 - status-UNCONFIRMED Bug#429934: [Fixed in 4.3] Incorrect type debugging information for variables in other compilation units Usertags were: status-UNCONFIRMED. Usertags are now: . > usertags 429934 + status-RESOLVED resolution-FIXED Bug#429934: [Fixed in 4.3] Incorrect type debugging information for variables in other compilation units There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package gnat-4.1
# # bts-link upstream status pull for source package gnat-4.1 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #246186 # * http://gcc.gnu.org/PR15799 # * remote status changed: WAITING -> NEW usertags 246186 - status-WAITING usertags 246186 + status-NEW # remote status report for #246387 # * http://gcc.gnu.org/PR15805 # * remote status changed: ASSIGNED -> RESOLVED # * remote resolution changed: (?) -> FIXED usertags 246387 - status-ASSIGNED usertags 246387 + status-RESOLVED resolution-FIXED # remote status report for #306834 # * http://gcc.gnu.org/PR21489 # * remote status changed: ASSIGNED -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 306834 + fixed-upstream usertags 306834 - status-ASSIGNED usertags 306834 + status-RESOLVED resolution-FIXED # remote status report for #408703 # * http://gcc.gnu.org/PR30618 # * remote status changed: UNCONFIRMED -> RESOLVED # * remote resolution changed: (?) -> FIXED usertags 408703 - status-UNCONFIRMED usertags 408703 + status-RESOLVED resolution-FIXED # remote status report for #429934 # * http://gcc.gnu.org/PR32452 # * remote status changed: UNCONFIRMED -> RESOLVED # * remote resolution changed: (?) -> FIXED usertags 429934 - status-UNCONFIRMED usertags 429934 + status-RESOLVED resolution-FIXED thanks
[bts-link] source package gcc-4.1
# # bts-link upstream status pull for source package gcc-4.1 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #424402 # * http://gcc.gnu.org/PR31944 # * remote status changed: UNCONFIRMED -> NEW usertags 424402 - status-UNCONFIRMED usertags 424402 + status-NEW thanks
Processed: Re: Bug#445793: orbit2cpp: FTBFS: CosNaming-cpp-common.cc:715: internal compiler error: in reference_to_unused, at dwarf2out.c:10010
Processing commands for [EMAIL PROTECTED]: > reassign 445793 gcc-4.2 Bug#445793: orbit2cpp: FTBFS: CosNaming-cpp-common.cc:715: internal compiler error: in reference_to_unused, at dwarf2out.c:10010 Bug reassigned from package `orbit2cpp' to `gcc-4.2'. > severity 445793 important Bug#445793: orbit2cpp: FTBFS: CosNaming-cpp-common.cc:715: internal compiler error: in reference_to_unused, at dwarf2out.c:10010 Severity set to `important' from `serious' > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
