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

please update autoconf/automake to more recent versions #42

Closed
doko42 opened this issue Jul 21, 2023 · 2 comments
Closed

please update autoconf/automake to more recent versions #42

doko42 opened this issue Jul 21, 2023 · 2 comments
Assignees

Comments

@doko42
Copy link

doko42 commented Jul 21, 2023

please update autoconf/automake to more recent versions, probably together with an update of libiberty to the current status of binutils/gcc trunk.

tschwinge added a commit that referenced this issue Jul 25, 2023
GCC commit a4ebe104540e7b6d3c637d793dbcd5171b4b8209 (Subversion r209988).

Co-authored-by: Thomas Schwinge <[email protected]>
tschwinge added a commit that referenced this issue Jul 25, 2023
GCC commit ac631cbe7021105c7fb8438deaeef66fe544b9aa (Subversion r238880).

Co-authored-by: Thomas Schwinge <[email protected]>
tschwinge added a commit that referenced this issue Jul 25, 2023
GCC commit 7e2de6df10b532be4e66025e318f68a0ebf2c408 (Subversion r265610).

Co-authored-by: Thomas Schwinge <[email protected]>
tschwinge added a commit that referenced this issue Jul 25, 2023
GCC commit 22e052725189a472e4e86ebb6595278a49f4bcdd (Subversion r265695).

Co-authored-by: Thomas Schwinge <[email protected]>
tschwinge added a commit that referenced this issue Jul 25, 2023
... following what we just imported:
GCC commit 22e052725189a472e4e86ebb6595278a49f4bcdd (Subversion r265695)
"Update GCC to autoconf 2.69, automake 1.15.1 (PR bootstrap/82856)".
tschwinge added a commit that referenced this issue Jul 25, 2023
GCC commit d7f00da1c0ed414175305c41a07b3a50fa577cce.

Co-authored-by: Thomas Schwinge <[email protected]>
tschwinge added a commit that referenced this issue Jul 25, 2023
GCC commit 5e431ae4ccc5fb0e077e598cb4efb1e12fc66c68.

Co-authored-by: Thomas Schwinge <[email protected]>
tschwinge added a commit that referenced this issue Jul 25, 2023
GCC commit 3d9439b1bb76c186958d5b86f0076f8b3017b8a2.

Co-authored-by: Thomas Schwinge <[email protected]>
tschwinge added a commit that referenced this issue Jul 25, 2023
GCC commit 86f64400a5692499856d41462461327b93f82b8d.

Co-authored-by: Thomas Schwinge <[email protected]>
tschwinge added a commit that referenced this issue Jul 25, 2023
GCC commit 7ff793415f55fa9a92f348fecb8c75ac8acc8b87.

Co-authored-by: Thomas Schwinge <[email protected]>
@tschwinge
Copy link
Member

In #1 (comment), @thesamesam had raised a similar request.

Over the past three days, I've now done several staged "Update imported files: GCC", and "Switch to Autoconf 2.69, Automake 1.15.1", plus some prerequisite cleanups and general streamlining. See https://github.com/MentorEmbedded/nvptx-tools/commits/2c6d5037ff5ecc36c02b9f17438c71622c76d163.

I hope that'll now serve us for another ten years; as per #1 (comment): "the libiberty/ (and also include/, for that matter) files correspond (modulo minor local changes) to those of GCC trunk r201139 (2013-07-22)" -- exactly ten years ago! ;-)

Please test (both @doko42 and @thesamesam), and if there are no issues, close this issue #42 then. (#1 "libiberty" will stay open until we've got that one sorted out generally.)

@tschwinge tschwinge self-assigned this Jul 25, 2023
tschwinge added a commit that referenced this issue Jul 30, 2023
…GCC, 2018-10-29 [#1, #42]"

..., that is, nvptx-tools commit 98e081c,
for GCC commit 7e2de6df10b532be4e66025e318f68a0ebf2c408 (Subversion r265610),
which, with 'ptxas' missing, changed, for example:

    $ ./nvptx-none-as --verify -o o test/as/bare-1.s
    nvptx-as: error trying to exec 'ptxas': execvp: No such file or directory
    nvptx-as: ptxas returned 255 exit status

..., to:

    $ ./nvptx-none-as --verify -o o test/as/bare-1.s
    nvptx-as: execvp: No such file or directory

Manually re-instantiate the lost piece of information.
@thesamesam
Copy link

A very late reply -- but it works well now indeed, thank you!

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

No branches or pull requests

3 participants