https://blog.modest-destiny.com/enContents © 2021 Adam Basfop Cavendish Mon, 22 Mar 2021 08:19:52 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://blog.modest-destiny.com/posts/undefined-reference-to-how-can-i-find-the-library-to-link-to/Adam Basfop Cavendish<div><p>The most panicking error among all the make errors is the <code>undefined reference</code> error, which is mostly cause by an unlinked library.</p> <p><a href="https://blog.modest-destiny.com/posts/undefined-reference-to-how-can-i-find-the-library-to-link-to/">Read more…</a> (1 min remaining to read)</p></div>BashCC++https://blog.modest-destiny.com/posts/undefined-reference-to-how-can-i-find-the-library-to-link-to/Tue, 12 May 2015 04:00:21 GMThttps://blog.modest-destiny.com/posts/gcc-build-with-strange-errors/Adam Basfop Cavendish<div><h2>GCC Build With Strange Errors</h2> <p>I have been fighting with these strange errors for some days, and finally I got it.</p> <h3>Problem</h3> <p>The core problem is that my <code>C_INCLUDE_PATH</code> and <code>CPLUS_INCLUDE_PATH</code> ends with a colon. Path ending with a colon will include current path, aka <code>./</code> which caused the error.</p> <p><a href="https://blog.modest-destiny.com/posts/gcc-build-with-strange-errors/">Read more…</a> (1 min remaining to read)</p></div>BashLinuxhttps://blog.modest-destiny.com/posts/gcc-build-with-strange-errors/Sun, 30 Nov 2014 04:00:44 GMT