<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #000000"><div data-marker="__QUOTED_TEXT__"><div>Hi Joel;<br></div><div><br></div><div data-marker="__QUOTED_TEXT__"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;" data-mce-style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;"><div><div style="font-family: 'arial' , 'helvetica' , sans-serif; font-size: 10pt; color: #000000;" data-mce-style="font-family: 'arial' , 'helvetica' , sans-serif; font-size: 10pt; color: #000000;"><br><div>BTW RTEMS uses GNU autotools differently in that it configures in one folder/directory and the builds targets into another folder is a very rare way of using autotools. I know this because I have downloaded and reviewed over 5000 open source projects for my new book.<br></div></div></div></blockquote><br><div>Funny because the core GNU tools like gcc, binutils, gdb plus newlib all allow out of tree builds. </div><br><div>It may be rare to use it this way but it works and leaves your source directory with no build artifacts. </div><br><div>It also allows having multiple builds from the same source tree simultaneously.</div><div><br data-mce-bogus="1"></div><div><strong>It's not an indictment of the RTEMS use of GNU Autotools that you build out of the configured folder. I am not sure why stating a truth may be offensive?</strong><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><strong>It was never a touchy point I was making, it was that for the purposes of debugging you can't use the online advice that people suggest to fix RTEMS configuration problems because the "build setup"</strong><br data-mce-bogus="1"></div><div><strong>(configuring in one folder, bulding targets in another) is not the TYPICAL way OTHERS use the GNU Autotools. So file finding in PATH searching works with different options.<br data-mce-bogus="1"></strong></div><div> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;" data-mce-style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;"><div><div style="font-family: 'arial' , 'helvetica' , sans-serif; font-size: 10pt; color: #000000;" data-mce-style="font-family: 'arial' , 'helvetica' , sans-serif; font-size: 10pt; color: #000000;"><br><div>Most GNU autotools projects configure IN THE FOLDER that they want to compile and archive source code. That's one reason why the problems of diagnosing RTEMS build configurations are harder.<br></div></div></div></blockquote><br><div>This is not required for autotools. It is just the default instructions. </div><div><br data-mce-bogus="1"></div><div><strong> When I read this I first thought I was talking to Richard Stallman. (LOL)</strong></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;" data-mce-style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid #cccccc; padding-left: 1ex;"><div><div style="font-family: 'arial' , 'helvetica' , sans-serif; font-size: 10pt; color: #000000;" data-mce-style="font-family: 'arial' , 'helvetica' , sans-serif; font-size: 10pt; color: #000000;"><br><div>Setting explicit file locations with absolute directories is a way to workaround the problems. <br></div><br><br><div>Cheers!<br></div><br><div>Daemondave on github<br></div><br><div>Check out my new book Untrapped Value on LeanPub: <a href="https://leanpub.com/untrappedvalue" target="_blank" rel="nofollow noopener noreferrer" data-mce-href="https://leanpub.com/untrappedvalue">https://leanpub.com/untrappedvalue</a><br data-mce-bogus="1"></div></div></div></blockquote></div></div><br></div></div></div></body></html>