https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #34 from commit-h...@freebsd.org ---
A commit references this bug:
Author: gerald
Date: Sun May 12 19:17:10 UTC 2019
New revision: 501438
URL: https://svnweb.freebsd.org/changeset/ports/501438
Log:
Forward port r499061 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #33 from commit-h...@freebsd.org ---
A commit references this bug:
Author: gerald
Date: Wed May 8 07:13:49 UTC 2019
New revision: 501002
URL: https://svnweb.freebsd.org/changeset/ports/501002
Log:
Update to the 20180503
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #32 from commit-h...@freebsd.org ---
A commit references this bug:
Author: gerald
Date: Sat Apr 27 14:47:53 UTC 2019
New revision: 500211
URL: https://svnweb.freebsd.org/changeset/ports/500211
Log:
MFH: r499061
Approved
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #31 from commit-h...@freebsd.org ---
A commit references this bug:
Author: gerald
Date: Mon Apr 15 23:08:04 UTC 2019
New revision: 499061
URL: https://svnweb.freebsd.org/changeset/ports/499061
Log:
GCC has two runtime
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Diane Bruce changed:
What|Removed |Added
Status|Open|Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #29 from Diane Bruce ---
(In reply to Yuri Victorovich from comment #28)
See my various notes on this subject.
https://people.freebsd.org/~db/libgcc.txt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Yuri Victorovich changed:
What|Removed |Added
CC||y...@rawbw.com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #27 from Michal Meloun ---
Hmm, it seems that symbol version problem is ARM specific.
It's introduced by this commit:
https://gcc.gnu.org/viewcvs/gcc?view=revision=128088
Unfortunately, commit log doesn't
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Michal Meloun changed:
What|Removed |Added
CC||m...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #25 from Diane Bruce ---
(In reply to Tijl Coosemans from comment #24)
I like this idea the best. It solves our current problem in all cases.
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #24 from Tijl Coosemans ---
Created attachment 179810
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179810=edit
remove -shared-libgcc from gfortran
Here's a patch for lang/gcc that removes use of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Mark Felder changed:
What|Removed |Added
CC||f...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #22 from Ian Lepore ---
I see a lot of talk here about fortran and USES=fortran as some sort of fix.
I'd just like to remind folks that this is not a fortran problem, it's a
generalized toolchain problem that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #20 from Diane Bruce ---
In comment #19 "It doesn't matter what compiler that port is compiled with
(including clang!) so there are no (simple) hacks you can add to files under Mk
or to cmake to detect this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Tijl Coosemans changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #18 from Diane Bruce ---
comment #17 good point.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #17 from Antoine Brodin ---
(In reply to Diane Bruce from comment #11)
Putting this workaround in compiler.mk will not solve the issue, USE_GCC=yes or
USES=fortran don't include compiler.mk
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #14 from gr...@kde.org ---
Received this work-around by private email:
I think I found a work-around that fixes *runtime* dynamic linking issues. I
added the following line to /etc/libmap.conf:
libgcc_s.so.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Kubilay Kocak changed:
What|Removed |Added
Priority|--- |Normal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Kubilay Kocak changed:
What|Removed |Added
Blocks||204598
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Kubilay Kocak changed:
What|Removed |Added
Keywords||needs-qa, patch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Kubilay Kocak changed:
What|Removed |Added
Blocks||196862, 205294
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Kubilay Kocak changed:
What|Removed |Added
Blocks||207750
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #12 from Diane Bruce ---
See https://people.freebsd.org/~db/libgcc_summary.txt
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Kubilay Kocak changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #11 from Diane Bruce ---
Simpler fix to compiler.mk
Index: compiler.mk
===
--- compiler.mk (revision 416615)
+++ compiler.mk (working copy)
@@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #10 from Diane Bruce ---
Sure. My original thought was it belonged in cmake.mk anyway! groot@ convinced
me it should go in cmake port itself and myself don't care.
The pkg-message is -Wl,-rpath=%%TARGLIB%%
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #9 from gr...@kde.org ---
.. so far, we've mostly been talking about ports, where the infrastructure
helps with inserting the right linker flags, and comment:7 points out that it
seems to DTRT. But what about non-ports builds?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #8 from gr...@kde.org ---
(In reply to Raphael Kubo da Costa from comment #7)
> lang/gcc's pkg-message says:
> > To ensure binaries built with this toolchain find appropriate versions
> > of the necessary run-time libraries,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #7 from Raphael Kubo da Costa ---
Created attachment 168925
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=168925=edit
Self-contained fortran+CMake example
To me, CMake does not seem to be doing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #6 from Diane Bruce ---
It also affects gcc from ports as well and not just gfortran, though the bug is
not as evident.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
gr...@kde.org changed:
What|Removed |Added
CC||gr...@kde.org
--- Comment #5 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Jeffrey Baitis changed:
What|Removed |Added
CC||j...@baitis.net
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Koop Mast changed:
What|Removed |Added
Assignee|freebsd-ports-bugs@FreeBSD. |k...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
Ian Lepore changed:
What|Removed |Added
CC||i...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120
--- Comment #2 from Diane Bruce ---
Uses/cmake.mk could be touched instead.
--- /usr/ports/Mk/Uses/cmake.mk 2016-03-17 15:49:04.0 -0400
+++ /usr/ports/Mk/Uses/cmake.mk.new 2016-03-13 12:36:39.0 -0400
36 matches
Mail list logo