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 problem was that at least one of the toolchains being built was a gcc3.3 and I didn't have a native gcc3.2, but the point I was trying to make was that I don't think this process can be made totally turn-key. There have to be example control scripts provided (demo.sh), but one has to have some understanding of what is in there. I think it is also nice when the provided configuration isn't necessary the most simple either, so showing that multiple toolchains can be built at the same time is a good thing I think. I was trying to say that I think demo.sh is good the way it is and each of us needs to put a little effort into learning to use it in a way that benefits the specific goal we have. ------ 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] |