Compilation issues in ISC DHCP-4.2.3

[Glenn Satchell]

The script named configure in the top-level of the source directory 
makes changes to the Makefiles. Generally the Makefile in each directory 
compiles the things in that directory.

SO at the top level of the source directory, you can run configure with 
the --help flag:

./configure --help
...
Some influential environment variables:
   CC          C compiler command
...

(The ... means I have skipped over some of the output)

To use a different compiler, say it's called xcc, you would use:

CC=xcc ./configure ...

This will then re-create the Makefiles with this new setting.

regards,
-glenn

On 06/08/12 22:32, ameen.shajahan at wipro.com wrote:
> Hi all,
>
> I am using ISC DHCP-4.2.3 for DHCP support.
>
> I want to compile and link ISC code in my server.
>
> By default gcc field in all Makefile is CC = gcc and BUILD_CC = gcc
>
> But I want to set the gcc field with my compiler.
>
> Also in ISC code there are lot of Makefiles available, So its very
> difficult to trace out which makefile needed actually to compile the ISC
> code.
>
> So I raised the below questions
>
> 1)How to change the gcc field in ISC code dynamically while running
>
> 2)What are all the makefiles actually needed to compile the ISC code. If
> I know what are all the makefile means , I can update the gcc field
> manually.
>
> Please provide the solution if anybody knows.
>
> Thanks,
>
> Ameen S
>
> *Please do not print this email unless it is absolutely necessary. *
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s)
> and may contain proprietary, confidential or privileged information. If
> you are not the intended recipient, you should not disseminate,
> distribute or copy this e-mail. Please notify the sender immediately and
> destroy all copies of this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com
>
>