Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gcc: re-add patch to fix relocation errors in libgomp dependants
Date: Sat, 29 Jun 2019 20:54:06 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12745@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 462 bytes --]

There is a new pull request by jnbr against master on the void-packages repository

https://github.com/jnbr/void-packages gcc
https://github.com/void-linux/void-packages/pull/12745

gcc: re-add patch to fix relocation errors in libgomp dependants
was previously added in 75fe6cb0497347aefead33b84a789897360a9116

It is needed at least for python3-Pillow on x86_64-musl

A patch file from https://github.com/void-linux/void-packages/pull/12745.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gcc-12745.patch --]
[-- Type: application/text/x-diff, Size: 1861 bytes --]

From 20fe107d636c8a185fd7025cee748547c4d2171b Mon Sep 17 00:00:00 2001
From: Johannes <johannes.brechtmann@gmail.com>
Date: Sat, 29 Jun 2019 20:48:39 +0200
Subject: [PATCH] gcc: re-add patch to fix relocation errors in libgomp
 dependants

was previously added in 75fe6cb0497347aefead33b84a789897360a9116

[ci skip]
---
 srcpkgs/gcc/patches/invalid_tls_model.patch | 26 +++++++++++++++++++++
 srcpkgs/gcc/template                        |  2 +-
 2 files changed, 27 insertions(+), 1 deletion(-)
 create mode 100644 srcpkgs/gcc/patches/invalid_tls_model.patch

diff --git a/srcpkgs/gcc/patches/invalid_tls_model.patch b/srcpkgs/gcc/patches/invalid_tls_model.patch
new file mode 100644
index 00000000000..598cde5cb3a
--- /dev/null
+++ b/srcpkgs/gcc/patches/invalid_tls_model.patch
@@ -0,0 +1,26 @@
+--- libgomp/configure.tgt	2018-11-08 18:13:04.000000000 +0100
++++ libgomp/configure.tgt	2019-06-29 20:06:31.972950350 +0200
+@@ -10,23 +10,6 @@
+ #  XCFLAGS		Add extra compile flags to use.
+ #  XLDFLAGS		Add extra link flags to use.
+ 
+-# Optimize TLS usage by avoiding the overhead of dynamic allocation.
+-if test $gcc_cv_have_tls = yes ; then
+-  case "${target}" in
+-
+-    *-*-k*bsd*-gnu*)
+-	;;
+-
+-    *-*-linux* | *-*-gnu*)
+-	XCFLAGS="${XCFLAGS} -ftls-model=initial-exec -DUSING_INITIAL_EXEC_TLS"
+-	;;
+-
+-    *-*-rtems*)
+-	XCFLAGS="${XCFLAGS} -ftls-model=local-exec"
+-	;;
+-  esac
+-fi
+-
+ # Since we require POSIX threads, assume a POSIX system by default.
+ config_path="posix"
+ 
diff --git a/srcpkgs/gcc/template b/srcpkgs/gcc/template
index 56d1cf38dd4..24ab2c31da9 100644
--- a/srcpkgs/gcc/template
+++ b/srcpkgs/gcc/template
@@ -8,7 +8,7 @@ _isl_version=0.19
 
 pkgname=gcc
 version=${_minorver}.0
-revision=1
+revision=2
 short_desc="GNU Compiler Collection"
 maintainer="Juan RP <xtraeme@voidlinux.org>"
 homepage="http://gcc.gnu.org"

             reply	other threads:[~2019-06-29 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-29 18:54 voidlinux-github [this message]
2019-06-29 20:04 ` voidlinux-github
2019-06-29 20:58 ` [PR PATCH] [Merged]: " voidlinux-github

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12745@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).