This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Joel, > I intend to start running the test suite on the installed tools as the > next step. Are you running it in the build tree or on installed images? The test suite runs in the build tree. I don't see any reason why it couldn't be made to work on installed images, though, if that is required. > I think we are better off trying to help Nick fix them. Small test > cases and offering to test are usually the best one can offer the maintainer > unless you are lucky enough to be able to actually fix it. :) OK, I'll try to get myself smartened up on the bug report stuff. > If you have fixes for 3.0.4 that are not in the current source, then we > need to work with Nick to get them merged. gcc-3.0.4 built out-of-the-box with only one small patch to the mcore.h file. I was about to post the patch when Nick nailed the bug himself. > In the meantime, if you want want to use the specs and build a mcore-elf > 3.0.4 RPM, we can talk offline about doing that and putting it on our > site. That might be best for now until we make some progress with the gcc mainline. As you say, better go offline with this one. Cheers, Brian ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |