Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade pynac to support gcc-11 #31694

Closed
mkoeppe opened this issue Apr 19, 2021 · 79 comments
Closed

Upgrade pynac to support gcc-11 #31694

mkoeppe opened this issue Apr 19, 2021 · 79 comments

Comments

@mkoeppe
Copy link
Contributor

mkoeppe commented Apr 19, 2021

(from #31786)

pynac fails to compile with gcc-11 (headers porting) pynac/pynac#375

... and ideally to consolidate the various patches added in #31679, #31645 etc.... as also requested in https://groups.google.com/g/sage-packaging/c/_vxPV7aKNjQ/m/b2-EdWP1BgAJ

When making a new release, also care should be taken to use a recent version of libtool that supports macOS Big Sur (see #31920).

CC: @dimpase @DaveWitteMorris @kiwifb @antonio-rojas

Component: packages: standard

Author: Dima Pasechnik, Matthias Koeppe

Branch: c9c50e3

Reviewer: Matthias Koeppe, Dima Pasechnik

Issue created by migration from https://trac.sagemath.org/ticket/31694

@mkoeppe mkoeppe added this to the sage-9.4 milestone Apr 19, 2021
@DaveWitteMorris
Copy link
Member

comment:1

There are still several pynac bug tickets that may not be hard to fix, so I think I will be posting quite a few more pynac patches in the next few months, so let's wait on this. But it would be good to make an upgrade before the 9.4 release.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 19, 2021

comment:2

Aren't you preparing your patches using git? I'd recommend to create pull requests to the pynac repo to make it more transparent.

@mkoeppe

This comment has been minimized.

@mkoeppe mkoeppe changed the title Upgrade pynac Upgrade pynac to support gcc-11 May 18, 2021
@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@dimpase
Copy link
Member

dimpase commented Jun 25, 2021

comment:7

I am going to cut a new release of pynac with all da patchez

@dimpase
Copy link
Member

dimpase commented Jun 25, 2021

Commit: e97c1b5

@dimpase
Copy link
Member

dimpase commented Jun 25, 2021

Branch: u/dimpase/packages/pynac/0.7.28

@dimpase
Copy link
Member

dimpase commented Jun 25, 2021

Author: Dima Pasechnik

@dimpase
Copy link
Member

dimpase commented Jun 25, 2021

New commits:

e97c1b5update pynac to 0.7.28

@kiwifb
Copy link
Member

kiwifb commented Jun 25, 2021

comment:9

Thank you Dima! :)

@antonio-rojas
Copy link
Contributor

comment:10

yah, thanks a lot!

@dimpase
Copy link
Member

dimpase commented Jun 25, 2021

comment:11

Dave, I've merged all your pynac patches into master, e.g.

pynac/pynac@9d442a8

while the log is clear they are yours, I'm still the author. If you like you can do a PR on github to change the author of these commits.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 25, 2021

comment:12

GH Actions run please

@dimpase
Copy link
Member

dimpase commented Jun 25, 2021

comment:13

Replying to @mkoeppe:

GH Actions run please

running at https://github.com/sagemath/sagetrac-mirror/actions/runs/972993967

@DaveWitteMorris
Copy link
Member

comment:14

Replying to @dimpase:

Dave, I've merged all your pynac patches into master, e.g.

pynac/pynac@9d442a8

while the log is clear they are yours, I'm still the author. If you like you can do a PR on github to change the author of these commits.

Thanks, Dima, that's great! I am not concerned about the "author", so nothing needs to be done, as far as I'm concerned.

Copying these patches to the pynac repository has been on my to-do list for a long time, but I never got around to it, so thanks for doing this! In the future, I'll try to save you (and the distro managers) some trouble by making the appropriate PRs.

@dimpase
Copy link
Member

dimpase commented Jun 26, 2021

comment:15

Replying to @DaveWitteMorris:

Copying these patches to the pynac repository has been on my to-do list for a long time, but I never got around to it, so thanks for doing this! In the future, I'll try to save you (and the distro managers) some trouble by making the appropriate PRs.

I guess you actually might have a git repo with these patches applied (at least this is how I typically do package patching), so it could have been a breeze to convert these into PRs. Anyway, it's done now.

@slel
Copy link
Member

slel commented Jun 26, 2021

comment:16

One can set the author name and email as different from the committer's:

$ git commit --author="Author Name <[email protected]>"

This can be used to amend the last commit done:

$ git commit --amend --author="Author Name <[email protected]>" --no-edit

Reference:

@sheerluck
Copy link
Contributor

comment:17

Replying to @dimpase:

Replying to @mkoeppe:

GH Actions run please

running at https://github.com/sagemath/sagetrac-mirror/actions/runs/972993967

gentoo failed bc system eclib wanted #31443

checking whether we can link and run a program using eclib...
eclib version 20210503, using NTL bigints and NTL real and complex multiprecision floating point
yes; use eclib from the system

@dimpase
Copy link
Member

dimpase commented Jun 27, 2021

comment:18

Replying to @dimpase:

Replying to @mkoeppe:

GH Actions run please

running at https://github.com/sagemath/sagetrac-mirror/actions/runs/972993967

looks like that everything (modulo the usual GH actions suspects, e.g. broken conda on some platforms) is working.
Review?

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 27, 2021

comment:19

Broken on ubuntu-trusty

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 28, 2021

comment:56

Dima, could you please make a release without PR 378, so that we can get this blocker ticket done? Just focused on what this ticket says - add support for gcc 11, consolidate existing patches; no breaking/removing of other platform support.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 28, 2021

comment:57

I volunteer to make the next pynac releases.

@dimpase
Copy link
Member

dimpase commented Jun 28, 2021

comment:58

Replying to @mkoeppe:

I volunteer to make the next pynac releases.

let's just drop gcc 4.x. It would minimise the disruption, and it's overdue anyway.

@DaveWitteMorris
Copy link
Member

comment:59

As I said on #32074, I am +1 on this proposal to drop support for gcc 4.x. That should solve the immediate problem.

@dimpase
Copy link
Member

dimpase commented Jun 28, 2021

comment:60

Or even better/quicker, just add AC_CHECK_FUNC(__builtin_smull_overflow,...) to spkg-configure for gcc spkg.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 28, 2021

comment:61

It's important to keep tickets focused. In particular for a blocker ticket like this one, which creates an urgency to get it in.

The urgent need to add support for gcc 11 is entirely unconnected to a decision to drop support for the gcc 4 versions used in some of our supported distributions.

It is poor practice to connect these two issues arbitrarily.

@dimpase
Copy link
Member

dimpase commented Jun 28, 2021

comment:62

our resources are limited;

  • making a new pynac release without __builtin_smull_overflow takes time,
  • re-doing the branch with __builtin_smull_overflow takes time
  • (and God help you finding a workaround not using __builtin_smull_overflow, potentially another time waste to keep a museum compiler in...)

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 28, 2021

comment:63

It's important to keep tickets focused -- that includes avoiding to give unsolicited advice to other developers regarding time management.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 30, 2021

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 30, 2021

Changed author from Dima Pasechnik to Dima Pasechnik, Matthias Koeppe

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 30, 2021

Changed commit from 11c80aa to c9c50e3

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 30, 2021

New commits:

c9c50e3build/pkgs/pynac: Upgrade to 0.7.29

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jun 30, 2021

Reviewer: Matthias Koeppe, ...

@dimpase
Copy link
Member

dimpase commented Jun 30, 2021

@dimpase
Copy link
Member

dimpase commented Jul 1, 2021

comment:68

lgtm

@dimpase
Copy link
Member

dimpase commented Jul 1, 2021

Changed reviewer from Matthias Koeppe, ... to Matthias Koeppe, Dima Pasechnik

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jul 1, 2021

comment:69

Thanks!

@vbraun
Copy link
Member

vbraun commented Jul 6, 2021

Changed branch from u/mkoeppe/packages/pynac/0.7.28 to c9c50e3

@dimpase
Copy link
Member

dimpase commented Jul 18, 2021

comment:71

I don't see this branch in the current develop branch, what's up?

@dimpase
Copy link
Member

dimpase commented Jul 18, 2021

Changed commit from c9c50e3 to none

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants