Binutils causes abnormally large, non-working binaries since 2.43
Bastiaan Timmer
basjetimmer@yahoo.com
Mon Feb 17 11:55:56 GMT 2025
More information about the Binutils mailing list
Mon Feb 17 11:55:56 GMT 2025
- Previous message (by thread): Binutils causes abnormally large, non-working binaries since 2.43
- Next message (by thread): Binutils causes abnormally large, non-working binaries since 2.43
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
(apologies for the noise, I believe I did not properly reply to the mailing list earlier, so just correcting that) I just realized: it is of course possible that just downgrading binutils is not enough. For example in my case, I noticed the size increase in a program I was linking against openssl. Just downgrading binutils would not fix this, unless I also recompiled openssl _after_ that downgrade. So, I of course don't know anything about that JVM, but maybe it is possible its size increase is due to one of its dependencies having bloated in size, and that needs to be rebuilt with the old binutils version first. kind regards, Bas On 17-02-2025 11:58, Julian Waters wrote: > Unfortunately even binutils 2.42 still yields a Java Virtual Machine > bloated to extreme sizes. It seems the 2 issues are unrelated. > > best regards, > Julian >
- Previous message (by thread): Binutils causes abnormally large, non-working binaries since 2.43
- Next message (by thread): Binutils causes abnormally large, non-working binaries since 2.43
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list