Forwarded conversationSubject:
Re: [Libffcall] Debug and cleanup projects------------------------
From: Sandeep K Chaudhary <address@hidden>
Date: Tue, Mar 4, 2014 at 12:01 PM
To: Avneet Kaur <address@hidden>, address@hidden
Hi Avneet,
Thanks for the reply ! I am experienced with working big code bases in C. I guess I should have formally introduced myself. Anyway, better late than never so here it goes :
I am a second year masters student in Computer Science at University of Waterloo in Canada. Before joining University of Waterloo, I worked for Cisco Systems and implemented networking features on their OS (written in C) . Before Cisco, I did my undergrads from IIT Guwahati in India. I am currently working improving tolerance against uncorrectable ECC errors in memory in the Linux kernel. This involves reading other's codes (most of the time), and writing patches and modules.
----------
From: Deepak Sharma <address@hidden>
Date: Tue, Mar 4, 2014 at 12:25 PM
To: Sandeep K Chaudhary <address@hidden>
On Tue, Mar 4, 2014 at 12:01 PM, Sandeep K Chaudhary
<
address@hidden> wrote:
>
> About the README file, I believe the installation procedure needs some
> modification
>
> " mkdir make
> cd make
> ./configure --cache-file=config.cache "
You are right Sandeep, I face same problem to. Apply "./configure
--cache-file=config.cache" outside make folder.
--
Deepak Kumar Sharma
Blog:
http://deekysharma.wordpress.com
----------
From: Sandeep K Chaudhary <address@hidden>
Date: Tue, Mar 4, 2014 at 12:36 PM
To: Deepak Sharma <address@hidden>
Hi Deepak,
The idea of creating the make directory is that you generate the new (executable and other related files) in this 'make' directory so as to keep files organized. So to meet that purpose, you can run './../configure
--cache-file=config.cache' from within the 'make' dir. If you run the make command outside of 'make' dir, there is no use of creating the 'make' dir.
Thanks,
Sandeep.