This is the mail archive of the gcc@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] | |
> On Wed, 25 Feb 2004, Richard Earnshaw wrote: > > The build system tries to build libmudflap with pthread calls. An arm-elf > > target is never going to support pthreads (it's for bare-metal systems). > > Consequently it's impossible to build the libjava or objc libraries. > > Libjava doesn't require pthreads to build (well, the build result isn't a > suitable Java implementation, but enough to test the compiler). > > I'm fairly certain libjava did build previously for arm-elf. If it > doesn't now, we have a regression. Sorry, I wasn't clear enough here. It didn't build libjava and libobjc because the build system died while trying to build libmudflap. I've no idea what mudflap is supposed to be for, so it's unclear to me whether it's an important part of the compiler or just another nice-to-have bolt on. The following patch just disables it from the build and does seem to solve the immediate problem of building the libraries. Whether or not this is the correct approach somebody else will have to judge. A better patch would probably move the gcc thread-detection code to the top level and use that do decide what the target capabilities were. <date> Richard Earnshaw <rearnsha@arm.com> * configure.in (arm-*-elf*): Don't build libmudflap.
Attachment:
mudflap.patch
Description: mudflap.patch
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |