Ok, I'm trying to build mspgcc-20111205 in windows with mingw.  I
successfully built binutils and gcc, although I had to manually specify
where to find gmp, mpfr, and mpc using -with-gmp=/usr/local ect.  When I try
and build gdb however, it fails.  Configure works fine, but when I 'make' it
eventually gives me this error:

 

gcc -DHAVE_CONFIG_H -DPROFILE=1 -DWITH_PROFILE=-1 -DDEFAULT_INLINE=0
-D_USE_MINGW_FSEEK -I. -I../../../../gdb-7.2/sim/msp430 -I../common \

-I../../../../gdb-7.2/sim/msp430/../common -I../../include
-I../../../../gdb-7.2/sim/msp430/../../include -I../../bfd \

-I../../../../gdb-7.2/sim/msp430/../../bfd -I../../opcodes
-I../../../../gdb-7.2/sim/msp430/../../opcodes -g -O2 -D__USE_MINW_ACCESS
-W1,--stack,8388608 -o run.exe \

run.o libsim.a ../../bfd/libbfd.a ../../opcodes/libopcodes.a -lintl
../../libiberty/libiberty.a -lm -lz

c:/mingw/bin/../lib/gcc/mingw32/4.6.1/../../../../mingw32/bin/ld.exe: cannot
find -lz

collect2: ld returned 1 exit status

make[3]: ***[run.exe] Error 1

make[3]: Leaving directory
'/c/Aaron/mspgcc/mspgcc-20111205/BUILD/gdb/sim/msp430'

blah

blah

. 

 

If I understand whats going on, its looking for a library called z which
doesn't seem to exist?  Does anyone know whats wrong?

 

Here is the configure command I used:

 

$ ../../gdb-7.2/configure --target=msp430 --prefix=/c/Aaron/mspgcc/msp430/
--with-gmp=/usr/local/ --with-mpc=/usr/local --with-mpfr=/usr/local 2>&1 |
tee co

 

And the make command:

 

$ make 2>&1 | tee mo

 

 

Aaron Murdoch

x3665

 

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Reply via email to