Re: [Mono-dev] Running autogen.sh from outside of source tree?
On 21/05/2014 21:39, Miguel de Icaza wrote: Hello, To build Mono with a different prefix, you need to use a tarball package, that has all of the bits that are not typically checked into git. Is there any documentation available on how to build the tarball package? Thanks, Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
No, because it is a common idiom for all automake/autoconf projects. Run autogen.sh on a clean tree, as direct on the instructions Then run make dist Miguel On Fri, May 23, 2014 at 8:54 AM, Alex J Lennon ajlen...@dynamicdevices.co.uk wrote: On 21/05/2014 21:39, Miguel de Icaza wrote: Hello, To build Mono with a different prefix, you need to use a tarball package, that has all of the bits that are not typically checked into git. Is there any documentation available on how to build the tarball package? Thanks, Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
On 23/05/2014 16:25, Miguel de Icaza wrote: No, because it is a common idiom for all automake/autoconf projects. Run autogen.sh on a clean tree, as direct on the instructions Then run make dist Miguel Many thanks ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
Hi, autogen.sh needs to be run from the tree, its configure+make which can be run out-of-tree. Zoltan On Wed, May 21, 2014 at 9:32 PM, Chris Morgan chmor...@gmail.com wrote: Hello. I'm trying to build mono under Yocto. Recently (so I've heard) there were some changes such that the autotools scripts are being run from outside of the source tree. I presume this is something like: cd mono mkdir monobuild cd monobuild ../autogen.sh [cmorgan@localhost monobuild]$ ../autogen.sh --prefix=/home/cmorgan/mono-prefix grep: configure.in: No such file or directory ../autogen.sh: line 125: mono/mini/Makefile.am: No such file or directory ../autogen.sh: line 126: mono/metadata/Makefile.am: No such file or directory Running aclocal -I m4 -I . ... aclocal: error: 'configure.ac' is required **Error**: aclocal failed. This may mean that you have not installed all of the packages you need, or you may need to set ACLOCAL_FLAGS to include -I $prefix/share/aclocal for the prefix where you installed the packages whose macros were not found This doesn't appear to work because several things in autogen.sh assume that the files are present in the current working directory. Some other steps however do use $srcdir. My question is whether it seems like a reasonable idea to correct autogen.sh to remove the assumption that builddir == sourcedir. If so then I'll go down this route and send a patch. If not then I'll use a Yocto work around for projects that don't/can't support doing that. I'm not big on papering over issues so I do prefer the first option but I didn't want to start work if it turns out that it may be a nearly impossible task. Chris ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
Hi Zoltan. No, I get that. The question is whether its possible to improve autogen.sh to support running out of tree by adding some more $srcdir entries, or whatever, at the appropriate locations. Chris On Wed, May 21, 2014 at 3:37 PM, Zoltan Varga var...@gmail.com wrote: Hi, autogen.sh needs to be run from the tree, its configure+make which can be run out-of-tree. Zoltan On Wed, May 21, 2014 at 9:32 PM, Chris Morgan chmor...@gmail.com wrote: Hello. I'm trying to build mono under Yocto. Recently (so I've heard) there were some changes such that the autotools scripts are being run from outside of the source tree. I presume this is something like: cd mono mkdir monobuild cd monobuild ../autogen.sh [cmorgan@localhost monobuild]$ ../autogen.sh --prefix=/home/cmorgan/mono-prefix grep: configure.in: No such file or directory ../autogen.sh: line 125: mono/mini/Makefile.am: No such file or directory ../autogen.sh: line 126: mono/metadata/Makefile.am: No such file or directory Running aclocal -I m4 -I . ... aclocal: error: 'configure.ac' is required **Error**: aclocal failed. This may mean that you have not installed all of the packages you need, or you may need to set ACLOCAL_FLAGS to include -I $prefix/share/aclocal for the prefix where you installed the packages whose macros were not found This doesn't appear to work because several things in autogen.sh assume that the files are present in the current working directory. Some other steps however do use $srcdir. My question is whether it seems like a reasonable idea to correct autogen.sh to remove the assumption that builddir == sourcedir. If so then I'll go down this route and send a patch. If not then I'll use a Yocto work around for projects that don't/can't support doing that. I'm not big on papering over issues so I do prefer the first option but I didn't want to start work if it turns out that it may be a nearly impossible task. Chris ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
So I'm just trying to find out if it seems feasible, at which point I'll go to it for a few and see if I can do so. Chris On Wed, May 21, 2014 at 3:39 PM, Chris Morgan chmor...@gmail.com wrote: Hi Zoltan. No, I get that. The question is whether its possible to improve autogen.sh to support running out of tree by adding some more $srcdir entries, or whatever, at the appropriate locations. Chris On Wed, May 21, 2014 at 3:37 PM, Zoltan Varga var...@gmail.com wrote: Hi, autogen.sh needs to be run from the tree, its configure+make which can be run out-of-tree. Zoltan On Wed, May 21, 2014 at 9:32 PM, Chris Morgan chmor...@gmail.com wrote: Hello. I'm trying to build mono under Yocto. Recently (so I've heard) there were some changes such that the autotools scripts are being run from outside of the source tree. I presume this is something like: cd mono mkdir monobuild cd monobuild ../autogen.sh [cmorgan@localhost monobuild]$ ../autogen.sh --prefix=/home/cmorgan/mono-prefix grep: configure.in: No such file or directory ../autogen.sh: line 125: mono/mini/Makefile.am: No such file or directory ../autogen.sh: line 126: mono/metadata/Makefile.am: No such file or directory Running aclocal -I m4 -I . ... aclocal: error: 'configure.ac' is required **Error**: aclocal failed. This may mean that you have not installed all of the packages you need, or you may need to set ACLOCAL_FLAGS to include -I $prefix/share/aclocal for the prefix where you installed the packages whose macros were not found This doesn't appear to work because several things in autogen.sh assume that the files are present in the current working directory. Some other steps however do use $srcdir. My question is whether it seems like a reasonable idea to correct autogen.sh to remove the assumption that builddir == sourcedir. If so then I'll go down this route and send a patch. If not then I'll use a Yocto work around for projects that don't/can't support doing that. I'm not big on papering over issues so I do prefer the first option but I didn't want to start work if it turns out that it may be a nearly impossible task. Chris ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
Hi, autogen.sh is designed to generate configure and Makefile.in files into the source tree, so they can be distributed. Generating them outside the source tree doesn't serve much purpose imho. Zoltan On Wed, May 21, 2014 at 9:54 PM, Chris Morgan chmor...@gmail.com wrote: So I'm just trying to find out if it seems feasible, at which point I'll go to it for a few and see if I can do so. Chris On Wed, May 21, 2014 at 3:39 PM, Chris Morgan chmor...@gmail.com wrote: Hi Zoltan. No, I get that. The question is whether its possible to improve autogen.sh to support running out of tree by adding some more $srcdir entries, or whatever, at the appropriate locations. Chris On Wed, May 21, 2014 at 3:37 PM, Zoltan Varga var...@gmail.com wrote: Hi, autogen.sh needs to be run from the tree, its configure+make which can be run out-of-tree. Zoltan On Wed, May 21, 2014 at 9:32 PM, Chris Morgan chmor...@gmail.com wrote: Hello. I'm trying to build mono under Yocto. Recently (so I've heard) there were some changes such that the autotools scripts are being run from outside of the source tree. I presume this is something like: cd mono mkdir monobuild cd monobuild ../autogen.sh [cmorgan@localhost monobuild]$ ../autogen.sh --prefix=/home/cmorgan/mono-prefix grep: configure.in: No such file or directory ../autogen.sh: line 125: mono/mini/Makefile.am: No such file or directory ../autogen.sh: line 126: mono/metadata/Makefile.am: No such file or directory Running aclocal -I m4 -I . ... aclocal: error: 'configure.ac' is required **Error**: aclocal failed. This may mean that you have not installed all of the packages you need, or you may need to set ACLOCAL_FLAGS to include -I $prefix/share/aclocal for the prefix where you installed the packages whose macros were not found This doesn't appear to work because several things in autogen.sh assume that the files are present in the current working directory. Some other steps however do use $srcdir. My question is whether it seems like a reasonable idea to correct autogen.sh to remove the assumption that builddir == sourcedir. If so then I'll go down this route and send a patch. If not then I'll use a Yocto work around for projects that don't/can't support doing that. I'm not big on papering over issues so I do prefer the first option but I didn't want to start work if it turns out that it may be a nearly impossible task. Chris ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
Its to avoid having to use autotools-broken vs. autotools scripts when building mono in Yocto. So yeah, not a big difference and its fixable by using autotools-broken but then that means the mono build is somehow broken heh Chris On Wed, May 21, 2014 at 3:57 PM, Zoltan Varga var...@gmail.com wrote: Hi, autogen.sh is designed to generate configure and Makefile.in files into the source tree, so they can be distributed. Generating them outside the source tree doesn't serve much purpose imho. Zoltan On Wed, May 21, 2014 at 9:54 PM, Chris Morgan chmor...@gmail.com wrote: So I'm just trying to find out if it seems feasible, at which point I'll go to it for a few and see if I can do so. Chris On Wed, May 21, 2014 at 3:39 PM, Chris Morgan chmor...@gmail.com wrote: Hi Zoltan. No, I get that. The question is whether its possible to improve autogen.sh to support running out of tree by adding some more $srcdir entries, or whatever, at the appropriate locations. Chris On Wed, May 21, 2014 at 3:37 PM, Zoltan Varga var...@gmail.com wrote: Hi, autogen.sh needs to be run from the tree, its configure+make which can be run out-of-tree. Zoltan On Wed, May 21, 2014 at 9:32 PM, Chris Morgan chmor...@gmail.com wrote: Hello. I'm trying to build mono under Yocto. Recently (so I've heard) there were some changes such that the autotools scripts are being run from outside of the source tree. I presume this is something like: cd mono mkdir monobuild cd monobuild ../autogen.sh [cmorgan@localhost monobuild]$ ../autogen.sh --prefix=/home/cmorgan/mono-prefix grep: configure.in: No such file or directory ../autogen.sh: line 125: mono/mini/Makefile.am: No such file or directory ../autogen.sh: line 126: mono/metadata/Makefile.am: No such file or directory Running aclocal -I m4 -I . ... aclocal: error: 'configure.ac' is required **Error**: aclocal failed. This may mean that you have not installed all of the packages you need, or you may need to set ACLOCAL_FLAGS to include -I $prefix/share/aclocal for the prefix where you installed the packages whose macros were not found This doesn't appear to work because several things in autogen.sh assume that the files are present in the current working directory. Some other steps however do use $srcdir. My question is whether it seems like a reasonable idea to correct autogen.sh to remove the assumption that builddir == sourcedir. If so then I'll go down this route and send a patch. If not then I'll use a Yocto work around for projects that don't/can't support doing that. I'm not big on papering over issues so I do prefer the first option but I didn't want to start work if it turns out that it may be a nearly impossible task. Chris ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
Hello, To build Mono with a different prefix, you need to use a tarball package, that has all of the bits that are not typically checked into git. That said, if you want to use git, you need to at least run this: NOCONFIGURE=1 ./autogen.sh On the directory where you did your checkout, and then you can run configure from a separate directory. On Wed, May 21, 2014 at 3:32 PM, Chris Morgan chmor...@gmail.com wrote: Hello. I'm trying to build mono under Yocto. Recently (so I've heard) there were some changes such that the autotools scripts are being run from outside of the source tree. I presume this is something like: cd mono mkdir monobuild cd monobuild ../autogen.sh [cmorgan@localhost monobuild]$ ../autogen.sh --prefix=/home/cmorgan/mono-prefix grep: configure.in: No such file or directory ../autogen.sh: line 125: mono/mini/Makefile.am: No such file or directory ../autogen.sh: line 126: mono/metadata/Makefile.am: No such file or directory Running aclocal -I m4 -I . ... aclocal: error: 'configure.ac' is required **Error**: aclocal failed. This may mean that you have not installed all of the packages you need, or you may need to set ACLOCAL_FLAGS to include -I $prefix/share/aclocal for the prefix where you installed the packages whose macros were not found This doesn't appear to work because several things in autogen.sh assume that the files are present in the current working directory. Some other steps however do use $srcdir. My question is whether it seems like a reasonable idea to correct autogen.sh to remove the assumption that builddir == sourcedir. If so then I'll go down this route and send a patch. If not then I'll use a Yocto work around for projects that don't/can't support doing that. I'm not big on papering over issues so I do prefer the first option but I didn't want to start work if it turns out that it may be a nearly impossible task. Chris ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
Hmm. I don't see any mention of NOCONFIGURE=1 in README.md. If it were possible to run autogen.sh from outside of tree it would make building under Yocto a little bit cleaner. Yocto is very particular about separating source from build from installed files so they can automate package generation, check for misbehaving packages etc. What is interesting is that a good portion of autogen.sh is ok with being run out of the source directory. Is it feasible to continue to improve autogen.sh to be run from outside of the source directory? If so, I can hack on it a bit tomorrow and see how I make out. Chris On Wed, May 21, 2014 at 4:39 PM, Miguel de Icaza mig...@xamarin.com wrote: Hello, To build Mono with a different prefix, you need to use a tarball package, that has all of the bits that are not typically checked into git. That said, if you want to use git, you need to at least run this: NOCONFIGURE=1 ./autogen.sh On the directory where you did your checkout, and then you can run configure from a separate directory. On Wed, May 21, 2014 at 3:32 PM, Chris Morgan chmor...@gmail.com wrote: Hello. I'm trying to build mono under Yocto. Recently (so I've heard) there were some changes such that the autotools scripts are being run from outside of the source tree. I presume this is something like: cd mono mkdir monobuild cd monobuild ../autogen.sh [cmorgan@localhost monobuild]$ ../autogen.sh --prefix=/home/cmorgan/mono-prefix grep: configure.in: No such file or directory ../autogen.sh: line 125: mono/mini/Makefile.am: No such file or directory ../autogen.sh: line 126: mono/metadata/Makefile.am: No such file or directory Running aclocal -I m4 -I . ... aclocal: error: 'configure.ac' is required **Error**: aclocal failed. This may mean that you have not installed all of the packages you need, or you may need to set ACLOCAL_FLAGS to include -I $prefix/share/aclocal for the prefix where you installed the packages whose macros were not found This doesn't appear to work because several things in autogen.sh assume that the files are present in the current working directory. Some other steps however do use $srcdir. My question is whether it seems like a reasonable idea to correct autogen.sh to remove the assumption that builddir == sourcedir. If so then I'll go down this route and send a patch. If not then I'll use a Yocto work around for projects that don't/can't support doing that. I'm not big on papering over issues so I do prefer the first option but I didn't want to start work if it turns out that it may be a nearly impossible task. Chris ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
On 22/05/14 02:20, Chris Morgan wrote: Hmm. I don't see any mention of NOCONFIGURE=1 in README.md. If it were possible to run autogen.sh from outside of tree it would make building under Yocto a little bit cleaner. Yocto is very particular about separating source from build from installed files so they can automate package generation, check for misbehaving packages etc. What is interesting is that a good portion of autogen.sh is ok with being run out of the source directory. Is it feasible to continue to improve autogen.sh to be run from outside of the source directory? If so, I can hack on it a bit tomorrow and see how I make out. IMHO this would be a good contribution (but I can't speak for mono maintainers). I've even seen some opensource projects which forbid building within the same tree, to avoid breaking out-of-tree builds by mistake. Out-of-tree builds also make it much easier to clean build artifacts (like the files that ./autogen.sh and ./configure generates), so another advantage of forcing out-of-tree builds is that .gitignore files get much simpler (i.e. just ignore build/*). ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Running autogen.sh from outside of source tree?
Well, Mono is not really well behaved when it comes to builds with srcdir != builddir. There is really no support for this for the managed code (all code under mono/mcs). On Wed, May 21, 2014 at 8:20 PM, Chris Morgan chmor...@gmail.com wrote: Hmm. I don't see any mention of NOCONFIGURE=1 in README.md. If it were possible to run autogen.sh from outside of tree it would make building under Yocto a little bit cleaner. Yocto is very particular about separating source from build from installed files so they can automate package generation, check for misbehaving packages etc. What is interesting is that a good portion of autogen.sh is ok with being run out of the source directory. Is it feasible to continue to improve autogen.sh to be run from outside of the source directory? If so, I can hack on it a bit tomorrow and see how I make out. Chris On Wed, May 21, 2014 at 4:39 PM, Miguel de Icaza mig...@xamarin.com wrote: Hello, To build Mono with a different prefix, you need to use a tarball package, that has all of the bits that are not typically checked into git. That said, if you want to use git, you need to at least run this: NOCONFIGURE=1 ./autogen.sh On the directory where you did your checkout, and then you can run configure from a separate directory. On Wed, May 21, 2014 at 3:32 PM, Chris Morgan chmor...@gmail.com wrote: Hello. I'm trying to build mono under Yocto. Recently (so I've heard) there were some changes such that the autotools scripts are being run from outside of the source tree. I presume this is something like: cd mono mkdir monobuild cd monobuild ../autogen.sh [cmorgan@localhost monobuild]$ ../autogen.sh --prefix=/home/cmorgan/mono-prefix grep: configure.in: No such file or directory ../autogen.sh: line 125: mono/mini/Makefile.am: No such file or directory ../autogen.sh: line 126: mono/metadata/Makefile.am: No such file or directory Running aclocal -I m4 -I . ... aclocal: error: 'configure.ac' is required **Error**: aclocal failed. This may mean that you have not installed all of the packages you need, or you may need to set ACLOCAL_FLAGS to include -I $prefix/share/aclocal for the prefix where you installed the packages whose macros were not found This doesn't appear to work because several things in autogen.sh assume that the files are present in the current working directory. Some other steps however do use $srcdir. My question is whether it seems like a reasonable idea to correct autogen.sh to remove the assumption that builddir == sourcedir. If so then I'll go down this route and send a patch. If not then I'll use a Yocto work around for projects that don't/can't support doing that. I'm not big on papering over issues so I do prefer the first option but I didn't want to start work if it turns out that it may be a nearly impossible task. Chris ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
