Thank you for the reply. In our case, the third party make system is being called as below:
*/usr/bin/env -i OCTEON_ROOT=</path/to/octeon_sdk> OCTEON_CPPFLAGS_GLOBAL_ADD=-DUSE_RUNTIME_MODEL_CHECKS=1 -DCVMX_ENABLE_PARAMETER_CHECKING=0 -DCVMX_ENABLE_CSR_ADDRESS_CHECKING=0 -DCVMX_ENABLE_POW_CHECKS=0 CC=mipsisa64-octeon-elf-gcc PATH=</path/to/some/executables> LD_LIBRARY_PATH=</some/lib/paths> make -C ../octeon_sdk/se_src/ipsec-gw * We have taken care that the environment starts afresh with the* -i* flag of *env*, and with this I believe, the CFLAGS or any other env variable is cleared. Is it right? What could possibly be the other cause for this? please thanks On Tue, Mar 8, 2011 at 8:26 AM, Luke Shumaker <[email protected]> wrote: > This is an ElectricMake issue, and this is a GNU Make mailing list, so > we may not be able to help you much. > > However, it sounds like ElectricMake is setting some environmental > variables that it passes to GNU Make. For example if the GNU Makefile > sets `CFLAGS+=-g' then when you run it from the command line, the > commands is `cc -g <whatever>', but if ElectricMake sets `CFLAGS=-Wall' > and exports it (in GNU Make terms), then in GNU Make CFLAGS will be > `-Wall -g', which would cause more errors to spit out. That of was an > example, there are a lot more compiler flags that could trip errors, and > other variables that will play with the system. > > -- > ~ LukeShu > http://lukeshu.ath.cx > > > On Tue, 2011-03-08 at 00:26 +0530, vkr wrote: > > *Strangely, When the build COMMAND TAKEN FROM BUILD LOG is run manually > > (bash shell), the execution completes without any errors or warnings > > mentioned above, and archiving works fine, too.* > > > > On Tue, Mar 8, 2011 at 12:25 AM, vkr <[email protected]> > wrote: > > > > > Hello. > > > > > > *Problem Description; * > > > A few rules to clean, and build third party build system(*octeon_sdk*) > > > (gnu make is being used to build the 3rd party stuff). > > > This 3rd party build system is being called from 'ElectricAccelerator's > > > emake tool'. That is, the whole lot of overall build gets started with > > > electric make, in which a component is this 3rd party build system. > > > > > > The compilation of an object file is working fine, but, we are ending > up > > > with warnings/errors while archiving. > > > similar to: > > > > > > Warning: size of symbol `' changed from 292 in > > > obj/libcvm-enet.a(cvm-enet-bridge.o) to 1060 in > > > obj/libcvm-enet.a(cvm-enetbridge.o) > > > and some multiple declarations of symbol `' and make is exiting with > > > error. > > > > > > *Strangely, When the build is run manually (bash shell), the execution > > > completes without any errors or warnings mentioned above, and archiving > > > works fine, too.* > > > > > > Please could any one let me know what could possibly be wrong with the > > > first approach, and how is it different when run manually, than running > it > > > from another make file? > > > > > > PS: The entire build system works perfect with IBM ClearMake. We are > > > porting the build system to ElectricMake, and we are seeing these > issues. > > > > > > Thanks, > > > > > > > > > > > > > > _______________________________________________ > > Help-make mailing list > > [email protected] > > http://lists.gnu.org/mailman/listinfo/help-make > > _______________________________________________ Help-make mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-make
