finds the WRONG libm.*
Dave
Cheers!
Daemondave on github
Check out my new book Untrapped Value on LeanPub: [
https://leanpub.com/untrappedvalue | https://leanpub.com/untrappedvalue ]
From: "Y. HB"
To: "DAVE ERICKSON"
Cc: "rtems-us...@rtems.org"
Sent:
n.
Dave
Cheers!
Daemondave on github
Check out my new book Untrapped Value on LeanPub: [
https://leanpub.com/untrappedvalue | https://leanpub.com/untrappedvalue ]
From: "Y. HB"
To: "joel"
Cc: "DAVE ERICKSON" , "rtems-us...@rtems.org"
Sent:
Hi Joel;
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.
Funny bec
nosing RTEMS
build configurations are harder.
Setting explicit file locations with absolute directories is a way to
workaround the problems.
Cheers!
Daemondave on github
Check out my new book Untrapped Value on LeanPub:
https://leanpub.com/untrappedvalue
From: "Joel Sherril
Hi Y.HB
LDFLAGS sets both the library kind to include in the archive build but it also
uses the -L flags to know where to look for it. The -lm can mean the libm.a.
libm.so libm.la so it searches the LD_LIBRARY_PATH environment variable to find
one that fits. If you want expressly to include th
