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: [PATCH v2] Fix libgfortran cross compile configury w.r.t newlib


On Oct 15, 2013, at 1:17 PM, Tobias Burnus <burnus@net-b.de> wrote:
> Marcus Shawcroft wrote:>> 2013-10-01  Marcus Shawcroft <marcus.shawcroft@arm.com>
> >>
> >>          * configure.ac (AC_CHECK_FUNCS_ONCE): Add for exit() then make
> >>          existing AC_CHECK_FUNCS_ONCE dependent on outcome.
> >
> > Ping^2
> 
> For configure patches, I am never quite sure whether they should be reviewed by a build maintainer or by the library maintainer. In any case, the change looks reasonable to me and as no other newlib user has complained, it is also okay from my side.

Would be nice for a build/config person to weigh in or to upgrade and make bullet proof the system against such failures.  My take, by default, the compile line should do something useful, and that should be enough for autoconf style tests to smell the library.  Now, we can observe that Steve's mips-mti-elf newlib port apparently violates that, but it is lost on me why that is and why that is a good thing.  Steve?  Is there some reason why by default, a suitable linker script can't be added by the compiler, or, if none suitable, a stub one that isn't suitable in general, but, is complete enough to allow autoconf to function normally?

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