mainAutoconf - Support: sr #110475, ranlib: plugin needed to handle...

 
 

sr #110475: ranlib: plugin needed to handle lto object

Submitter:  R. Diez <rdiez>
Submitted:  Thu 22 Apr 2021 07:32:38 AM UTC
   
 
Priority:  * 5 - Unprioritized Severity:  3 - Normal
Status:  Not Autoconf Privacy:  Public
Assigned to:  None Open/Closed:  Closed
Operating System:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 08 Dec 2023 05:24:07 PM UTC, comment #4: 

Closing.

R. Diez, please understand that it really does need to be you who files the bug against Automake, so that you are in direct communication with the Automake developers, rather than having us as go-betweens.  Detailed instructions for reporting bugs with Automake can be found here: https://www.gnu.org/software/automake/manual/html_node/Reporting-Bugs.html

Zack Weinberg <zackw>
Group administrator
Sun 03 Dec 2023 12:42:14 PM UTC, comment #3: 

the Automake homepage explains where to file bugs:
https://www.gnu.org/software/automake/

and the Savannah page has it under "mailing lists".

Savannah doesn't let us customize the "support" page, and some Automake devs don't want to use a web-based bug tracker.

so this report can't be moved to a diff project, it has to be refiled.

Mike Frysinger <vapier>
Group Member
Sun 03 Dec 2023 10:22:19 AM UTC, comment #2: 

I am sorry I reported this issue against Autoconf then. I am no expert in Autoconf/Automake, and I often find it difficult to pin-point where such problems are coming from.

I found the following development site for Automake:

https://savannah.gnu.org/git/?group=automake

But there is no "Support" link to report bugs, like in this project. I haven't really have the time now to deal with project bureaucracy.

About attaching an example, I'm afraid I haven't got a small, easy example to attach. My project has moved to this location:

https://github.com/rdiez/DebugDue/

This is where I had to add the workaround:

https://github.com/rdiez/DebugDue/blob/f61f3c4491efee5d01f692a2d50c2cc1bf43c9f1/DebugDueBuilder.sh#L502

If the link does not work, search for "AR=" in the project's shell scripts.

In order to test it, you would have to build a cross-compilation toolchain first, so it is not really suitable as an easy example.

Anyway, the problem this bug report is about is rather popular and obvious, and I did include links from other such reports on the Internet. I am surprised that you haven't got tons of duplicate bug reports about this.

I cannot find a way to change the status of this bug report, or close it. I do not know why either. This Savannah system is not really helpful in this respect.

R. Diez <rdiez>
Sun 03 Dec 2023 04:08:35 AM UTC, comment #1: 

this prob should be reported to automake instead

also it'd help if you attached examples in your reports

Mike Frysinger <vapier>
Group Member
Thu 22 Apr 2021 07:32:38 AM UTC, original submission:  

More and more people are building software with GCC's LTO nowadays.

I recently added a very simple library called libAtmelSoftwareFramework.a to this cross-compilation project of mine:

https://github.com/rdiez/JtagDue/blob/master/Project/Makefile.am

Then I got this error:

arm-none-eabi-ranlib: libAtmelSoftwareFramework.a(libAtmelSoftwareFramework_a-system_sam3x.o): plugin needed to handle lto object

The fix I came up with is to edit my top-level build script in order to add the following arguments to the ./configure invocation:

AR=$TARGET_ARCH-gcc-ar
RANLIB=$TARGET_ARCH-gcc-ranlib

This has been a known issue for years. There are many discussions on the Internet. As a new Autoconf user, you have to search for the error message and read here and there. Example pages:

https://stackoverflow.com/questions/40374061/autoconf-recipe-to-use-gcc-ar-and-gcc-ranlib

https://bugzilla.redhat.com/show_bug.cgi?id=1467409

I think it is time for Autoconf to do something about this, instead of letting everybody lose time all over the place.

At the very least, this shortcoming should be documented in the Autoconf manual. Failing that, the FAQ page should mention it.

Autoconf already knows that it should not link directly with ld, so that it uses gcc as a linker wrapper, presumably because of similar issues. Is there any reason why Autoconf could not learn to use such gcc wrappers for ar and ranlib too?

R. Diez <rdiez>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by zackw (Posted a comment)
  • -email is unavailable- added by vapier (Posted a comment)
  • -email is unavailable- added by rdiez (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-12-08 zackw Open/ClosedOpen Closed
    2023-12-03 vapier StatusNone Not Autoconf

    Back to the top

    Powered by Savane 3.13-c54d.
    Corresponding source code