This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [libiberty] Cleanup of configure part 1


Isn't that overkill for a change that produces no semantic differences in the generated configure script?

Perhaps, but he *did* test it with a native bootstrap, and most libiberty configure bugs don't show up in a native anyway.

My initial reaction was the same as Zack's, but there is a slight potential for problems creeping in with the removal of accross.m4.


I tested both changes performed a --with-newlib i686-pc-gnu-linux -> powerpc-elf-unknown cross. It built libstdc++ and newlib in a multilib configuration.

For the build libiberty (libiberty/):
A comparison before and after the changes after stripping showed all objects to be identical.
libiberty.a only differed in the unix timestamps that they were added.

For the target libiberty (powerpc-unknown-elf/libiberty):
A comparison before and after the changes after stripping showed all the elf32-big objects to be the identical.
libiberty.a only differed in the unix timestamps that they were added.

OK to install?




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]