[Bug 1026181] New: gcc6-java, gcc6-objc, gcc6-obj-c++ are out of date
http://bugzilla.opensuse.org/show_bug.cgi?id=1026181 Bug ID: 1026181 Summary: gcc6-java, gcc6-objc, gcc6-obj-c++ are out of date Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: rguenther@suse.com Reporter: schwab@linux-m68k.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- While gcc6 has been updated to 6.2.1, gcc6-java, gcc6-objc and gcc6-obj-c++ are still at 6.1.1. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1026181 http://bugzilla.opensuse.org/show_bug.cgi?id=1026181#c1 Richard Biener <rguenther@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com, | |meissner@suse.com --- Comment #1 from Richard Biener <rguenther@suse.com> --- I don't remember issueing an update for gcc6 for 42.2 so somebody else f**ed up here (in not releasing all sub-packages built). I guess as usuall whoever did the update needs to re-do it properly. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1026181 http://bugzilla.opensuse.org/show_bug.cgi?id=1026181#c3 --- Comment #3 from Ludwig Nussel <lnussel@suse.com> --- The SP2 package unconditionally sets build_optional_compiler_languages=1 which has the interesting logic of disabling java and objc builds. That also affects 42.3 which lacks objc now. gcc6-java comes from a separate package libgcj-gcc6 that does not exist on SLE. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1026181 http://bugzilla.opensuse.org/show_bug.cgi?id=1026181#c6 --- Comment #6 from Andreas Schwab <schwab@linux-m68k.org> --- I don't understand your question. This bug is about 42.2. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1026181 http://bugzilla.opensuse.org/show_bug.cgi?id=1026181#c7 --- Comment #7 from Andreas Schwab <schwab@linux-m68k.org> --- Sorry, I didn't realize that the question was directed to astieger. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1026181 http://bugzilla.opensuse.org/show_bug.cgi?id=1026181#c8 --- Comment #8 from Ludwig Nussel <lnussel@suse.com> --- Every single binary in the system uses the gcc6 runtime. I'd assume that sharing that with SLE is the safe choice. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1026181 http://bugzilla.opensuse.org/show_bug.cgi?id=1026181#c11 --- Comment #11 from Richard Biener <rguenther@suse.com> --- (In reply to Marcus Meissner from comment #10)
Talked with Ludwig.
- continue to use SLES 12 SP2 gcc6 sources - adjusted change_spec to match what we need to build for Leap 42.2.
- should flow back to SLES 12 SP2 gcc6 with if conditionals
Err - change_spec changes plus ./pre-checkin.sh result in additional spec files, how do you handle this "with if conditionals"!? So, for sure not. Looks like you need to live with divergent sources then. Your decision. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1026181 http://bugzilla.opensuse.org/show_bug.cgi?id=1026181#c12 --- Comment #12 from Andreas Schwab <schwab@linux-m68k.org> --- With the latest update the libasan3, libatomic1, libcilkrts5, libgomp1, libitm1, liblsan0, libmpx2, libmpxwrappers2, libtsan0, libubsan0, libgcj-bc1 packages have lost their -gcc6 suffix, and they all conflict with themselves. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1026181 http://bugzilla.opensuse.org/show_bug.cgi?id=1026181#c13 Richard Biener <rguenther@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #13 from Richard Biener <rguenther@suse.com> --- (In reply to Andreas Schwab from comment #12)
With the latest update the libasan3, libatomic1, libcilkrts5, libgomp1, libitm1, liblsan0, libmpx2, libmpxwrappers2, libtsan0, libubsan0, libgcj-bc1 packages have lost their -gcc6 suffix, and they all conflict with themselves.
That's how it supposed to be. (they conflict with "otherproviders" of themselves) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com