[Mono-dev] Re: Makefile in runtime causing problems

Robert Jordan robertj at gmx.net
Fri Apr 7 18:18:37 EDT 2006


James,

> In the svn repository now is a configure script which creates a
> Makefile in the runtime directory that has mcs_topdir and
> mcs_topdir_from_srcdir variables (what are these variables exactly?)
> They cause my makes to fail.

Have a look at mono/README. You also need mcs and libgdiplus from SVN.

Robert

> 
> Here's what happens after a run of make:
> 
> $ make
> ... blah blah blah...
> 
> Making all in net_2_0
> make[3]: Entering directory `/home/james/source/mono/mono/data/net_2_0'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/home/james/source/mono/mono/data/net_2_0'
> make[3]: Entering directory `/home/james/source/mono/mono/data'
> make[3]: Nothing to be done for `all-am'.
> make[3]: Leaving directory `/home/james/source/mono/mono/data'
> make[2]: Leaving directory `/home/james/source/mono/mono/data'
> Making all in runtime
> make[2]: Entering directory `/home/james/source/mono/mono/runtime'
> d=`cd ../support && pwd`; \
> sed 's,target="libMonoPosixHelper[^"]*",target="'$d/libMonoPosixHelper.la'",'
> .. /data/config > wrapper-config
> if test -z ""; then :; else \
>   mv wrapper-config wrapper-configt; \
>   sed 's,<configuration>,& <dllmap dll="gdiplus.dll" target="" />,'
> wrapper-conf igt > wrapper-config; \
>   rm -f wrapper-configt; \
> fi
> if test -w ../../mcs; then :; else chmod -R +w ../../mcs; fi
> chmod: cannot access `../../mcs': No such file or directory
> make[2]: *** [all-local] Error 1
> make[2]: Leaving directory `/home/james/source/mono/mono/runtime'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/james/source/mono/mono'
> make: *** [all] Error 2
> james at athlon64:~/source/mono/mono>
> 
> 
> Does anyone know how I can fix this? Are the mcs_topdir and
> mcs_topdir_from_srcdir variables meant to point to the absolute source
> directory path for mcs in the source repository being built and the
> relative path to it respectively? If yes where are they in the source
> repository? Also when configure ran after ./autogen.sh it assumed I
> already had libgdi+, which is correct, but isn't the repository meant
> to build a new one or something? After just checking out 'mono' from
> svn, what is actually built?
> 
> Thanks,
> James




More information about the Mono-devel-list mailing list