[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

--- Comment #14 from commit-h...@freebsd.org ---
A commit references this bug:

Author: jbeich
Date: Tue Jan  3 08:55:57 UTC 2017
New revision: 430446
URL: https://svnweb.freebsd.org/changeset/ports/430446

Log:
  cad/openvsp: drop 10.1 workaround (revert r428665) per EOL

  PR:   214863 215307
  Approved by:  portmgr blanket

Changes:
  head/cad/openvsp/Makefile

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

--- Comment #12 from Antoine Brodin  ---
(In reply to Jan Beich (mail not working) from comment #11)
Unless the FreeBSD Security Officer changes his mind,  at 23:59 UTC December
31, 2016, FreeBSD 9.3, 10.1 and 10.2 will reach end-of-life and will no longer
be supported.

So 2017Q1 will not support those releases (unless so@ changes his mind).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

--- Comment #11 from Jan Beich (mail not working)  ---
What's portmgr's plan for quarterly? Will 2017Q1 still support 9.x, 10.1, 10.2
and tag RELEASE_9_EOL at the end?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

Jan Beich (mail not working)  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2151
   ||92

--- Comment #10 from Jan Beich (mail not working)  ---
devel/libcxxrt workaround would be no better than lang/gcc48. One has to make
sure RPATH works properly or backward compatibility would fail due to multiple
layers of indirection (see libgcc_s vs. libgfortran mess).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

--- Comment #9 from Baptiste Daroussin  ---
well this is a bug :)

They should not

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

Dimitry Andric  changed:

   What|Removed |Added

 CC||b...@freebsd.org

--- Comment #8 from Dimitry Andric  ---
One question though: why are ports on 10.x using devel/libc++, while libc++ is
in base?  I would really like to understand the reasoning behind this.  IIRC
Baptiste added it, so I'm putting him on the CC list.

Another way to fix this would be to make the ports that use devel/libc++, also
use devel/libcxxrt, in which this problem has already been fixed.  E.g, change
the devel/libc++ port so the /usr/local/lib/c++/libstdc++.so linker scripts it
installs contains:

GROUP ( /usr/local/lib/libc++.so.1 /usr/local/lib/libcxxrt.so )

and add devel/libcxxrt as a dependency of devel/libc++.

This is far easier than an EN, and this workaround can be removed as soon as
9.x and 10.[12] reach end of life.  In fact, we should actively try to remove
the whole devel/libc++ and devel/libcxxrt ports in the future.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

--- Comment #6 from Mathieu Arnold  ---
Up until a branch is out of support, it should get all the EN/SA that we
promise. So any EN/SA that comes out before January 1st should include 10.1 and
10.2 (and 9.3 if applicable)

Now, after the support runs out, we should really not support them any more,
otherwise, people will start expecting our EOL to be automatically extended,
and I am not sure secteam@ or re@ has the manpower to handle that.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

Ed Maste  changed:

   What|Removed |Added

 CC||ema...@freebsd.org

--- Comment #5 from Ed Maste  ---
> 10.1 and 10.2 have one month of life left... Do you really think this is worth
> the trouble?

Regardless of the branches still being supported today, some of our downstream
consumers continue to use FreeBSD releases long after they're no longer
supported. I think there is value in an EN even if the branch is EOL at the end
of the year. I can't really say for sure that this is enough value to justify
the effort: I suspect those downstream users don't follow -pN releases directly
anyhow and it's easy enough for them to incorporate the patch into their local
tree.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

--- Comment #4 from Dimitry Andric  ---
(In reply to David Chisnall from comment #3)
> It would be good to put out an EN for the libcxxrt change and merge it back
> to all supported branches - the same problem will occur if you are using a
> recent clang on these systems.

10.1 and 10.2 have one month of life left... Do you really think this is worth
the trouble?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

David Chisnall  changed:

   What|Removed |Added

 CC||thera...@freebsd.org

--- Comment #3 from David Chisnall  ---
It would be good to put out an EN for the libcxxrt change and merge it back to
all supported branches - the same problem will occur if you are using a recent
clang on these systems.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

Jan Beich (mail not working)  changed:

   What|Removed |Added

 CC||port...@freebsd.org
 Attachment #177468||maintainer-approval?(portmg
  Flags||r...@freebsd.org)

--- Comment #2 from Jan Beich (mail not working)  ---
Created attachment 177468
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=177468=edit
gcc48 workaround

Maybe dangerous if USES=compiler:gcc-c++11-lib is mixed with USES=fortran in
dependencies. I've only tested direct consumers. graphics/GraphicsMagick had to
be patched to avoid breaking science/gnudatalanguage: http://sprunge.us/bMYN

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863

Bug ID: 214863
   Summary: lang/gcc + libc++ may fail due to spurious
__cxa_throw_bad_array_new_length reference
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Keywords: regression
  Severity: Affects Only Me
  Priority: ---
 Component: Individual Port(s)
  Assignee: ger...@freebsd.org
  Reporter: jbe...@freebsd.org
CC: freebsd-toolchain@FreeBSD.org
Blocks: 196712
 Flags: maintainer-feedback?(ger...@freebsd.org)
  Assignee: ger...@freebsd.org

Bug 196712 regressed USES=compiler:gcc-c++11-lib ports. gcc49 or later appear
to have the following regression on /releng/10.1. Maybe toolchain@ has a clue.

  $ cat a.cc
  int main()
  {
// Snippet from lilypond-devel
int argc = 5;
char **argv = new char*[argc + 2];
return 0;
  }

  $ pkg install -y gcc libc++
  $ g++49 -std=c++11 -nostdinc++ -isystem /usr/local/include/c++/v1
-L/usr/local/lib/c++ a.cc
  /tmp//ccZYfujU.o: In function `main':
  a.cc:(.text+0x2b): undefined reference to `__cxa_throw_bad_array_new_length'
  collect2: error: ld returned 1 exit status

Affected ports:

  cad/openvsp
  math/ceres-solver
  math/saga
  print/lilypond-devel


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196712
[Bug 196712] exp-run: Update lang/gcc from GCC 4.8 to GCC 4.9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"