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] |
> yes. The greps wouldn't be needed if patch were better about > returning nonzero status on failed patches. patch -p1 -f --dry-run should exit 0 if applied successfully even with fuzz...else exit 1 I haven't done too much checking to see how reliable it is though... > > If so I wonder if it is more desireable to skip the patch and continue > > patching all that will apply to the sources or to bail out of the > > patch/build process entirely. > > I'm too paranoid for that. If anything goes wrong, it's > totally unexpected, and who knows what will happen, so best abort. > I don't want anyone complaining that crosstool is flaky. Yep...I would be as well...good call. Also, I am finally reporting success using crosstool to do a big-endian (default) gcc-3.4.0 + glibc-2.3.2 cross for XScale - IXP425. Been fighting it for a while...may have ended up being that arm strlen patch. I will report in a following email for benefit of the list. Do you know off hand whether glibc-2.2.5 needed that patch?...I will dig in and find out but just curious if you ran across it. Thanks! -Dave > - Dan > > -- > My technical stuff: http://kegel.com > My politics: see http://www.misleader.org for examples of why I'm for regime change > ------ 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] |