How is the release tarball (that doesn’t require ATS 1 and just needs ./configure; make; make install) generated from the git sources? I’m poking around Makefile_devl now to try to build it in-tree but I’d like to know how to make a fake local release to test any changes I might want to make fully.
cd ${PATSHOME}; make CBOOT
cd ${PATSHOME}/doc/DISTRIB; make atspackaging; make atspacktarzvcfOn Thursday, April 16, 2015 at 5:09:09 AM UTC-4, Shea Levy wrote:
Hi all,
How is the release tarball (that doesn’t require ATS 1 and just needs
./configure; make; make install) generated from the git sources? I’m poking
around Makefile_devl now to try to build it in-tree but I’d like to know
how to make a fake local release to test any changes I might want to make
fully.
Did you set ATSHOMERELOC to ‘ATS-0.2.12’ ?On Sat, Apr 18, 2015 at 10:37 AM, Shea Levy sh...@shealevy.com wrote:
Yes, I just discovered that. Now I get a lot of errors like this building
the resulting tarball:
pats_main_dats.o: In function _2nix_2tmp_2nix_2dbuild_2dATS2_2dPostiats_2etgz_2edrv_2d10_2ATS_2dPostiats_2src_2pats_main_2edats__staload': pats_main_dats.c:(.text+0x14af): undefined reference to ATS_2d0_2e2_2e12_2libc_2SATS_2stdio_2esats__staload’
There appear to be missing references to libc and libats functions, even
though those are compiled.
cd ${PATSHOME}; make CBOOT
cd ${PATSHOME}/doc/DISTRIB; make atspackaging; make atspacktarzvcf
On Thursday, April 16, 2015 at 5:09:09 AM UTC-4, Shea Levy wrote:
Hi all,
How is the release tarball (that doesn’t require ATS 1 and just needs
./configure; make; make install) generated from the git sources? I’m poking
around Makefile_devl now to try to build it in-tree but I’d like to know
how to make a fake local release to test any changes I might want to make
fully.
make -C src/CBOOT/prelude
make -C src/CBOOT/libc
make -C src/CBOOT/libatsOn Saturday, April 18, 2015 at 9:25:20 AM UTC-4, Shea Levy wrote:
Hi all,
In a fresh checkout (on top of my recent pull request 1), I ran:
make -C src/ -f Makefile CBOOT
make -C doc/DISTRIB atspackaging
make -C doc/DISTRIB atspacktarzvcf
And then tried to build the resulting tarball the normal way. It failed
with:
make1: *** No rule to make target ‘prelude_basics_sta_sats.o’, needed by
‘prelude_libats.o’. Stop.
How am I meant to properly generate the needed files/rules?
Thanks,
Shea
On Apr 16, 2015, at 10:57 AM, gmhwxi <gmh...@gmail.com <javascript:>> wrote:
Here are the commands you need:
cd ${PATSHOME}; make CBOOT
cd ${PATSHOME}/doc/DISTRIB; make atspackaging; make atspacktarzvcf
On Thursday, April 16, 2015 at 5:09:09 AM UTC-4, Shea Levy wrote:
Hi all,
How is the release tarball (that doesn’t require ATS 1 and just needs
./configure; make; make install) generated from the git sources? I’m poking
around Makefile_devl now to try to build it in-tree but I’d like to know
how to make a fake local release to test any changes I might want to make
fully.
Thanks!> On Apr 16, 2015, at 10:57 AM, gmhwxi gmh...@gmail.com wrote:
Here are the commands you need:
cd ${PATSHOME}; make CBOOT
cd ${PATSHOME}/doc/DISTRIB; make atspackaging; make atspacktarzvcf
On Thursday, April 16, 2015 at 5:09:09 AM UTC-4, Shea Levy wrote:
Hi all,
How is the release tarball (that doesn’t require ATS 1 and just needs ./configure; make; make install) generated from the git sources? I’m poking around Makefile_devl now to try to build it in-tree but I’d like to know how to make a fake local release to test any changes I might want to make fully.
Yes, I just discovered that. Now I get a lot of errors like this building the resulting tarball:
pats_main_dats.o: In function _2nix_2tmp_2nix_2dbuild_2dATS2_2dPostiats_2etgz_2edrv_2d10_2ATS_2dPostiats_2src_2pats_main_2edats__staload': pats_main_dats.c:(.text+0x14af): undefined reference to ATS_2d0_2e2_2e12_2libc_2SATS_2stdio_2esats__staload’
There appear to be missing references to libc and libats functions, even though those are compiled.> On Apr 18, 2015, at 10:31 AM, gmhwxi gmh...@gmail.com wrote:
I think you also need:
make -C src/CBOOT/prelude
make -C src/CBOOT/libc
make -C src/CBOOT/libats
On Saturday, April 18, 2015 at 9:25:20 AM UTC-4, Shea Levy wrote:
Hi all,
In a fresh checkout (on top of my recent pull request 1), I ran:
make -C src/ -f Makefile CBOOT
make -C doc/DISTRIB atspackaging
make -C doc/DISTRIB atspacktarzvcf
And then tried to build the resulting tarball the normal way. It failed with:
make1: *** No rule to make target ‘prelude_basics_sta_sats.o’, needed by ‘prelude_libats.o’. Stop.
How am I meant to properly generate the needed files/rules?
cd ${PATSHOME}; make CBOOT
cd ${PATSHOME}/doc/DISTRIB; make atspackaging; make atspacktarzvcf
On Thursday, April 16, 2015 at 5:09:09 AM UTC-4, Shea Levy wrote:
Hi all,
How is the release tarball (that doesn’t require ATS 1 and just needs ./configure; make; make install) generated from the git sources? I’m poking around Makefile_devl now to try to build it in-tree but I’d like to know how to make a fake local release to test any changes I might want to make fully.
cd ${PATSHOME}; make CBOOT
cd ${PATSHOME}/doc/DISTRIB; make atspackaging; make atspacktarzvcf
On Thursday, April 16, 2015 at 5:09:09 AM UTC-4, Shea Levy wrote:
Hi all,
How is the release tarball (that doesn’t require ATS 1 and just needs ./configure; make; make install) generated from the git sources? I’m poking around Makefile_devl now to try to build it in-tree but I’d like to know how to make a fake local release to test any changes I might want to make fully.
Ah ha, that did it! Thank you.> On Apr 18, 2015, at 10:42 AM, Hongwei Xi gmh...@gmail.com wrote:
Did you set ATSHOMERELOC to ‘ATS-0.2.12’ ?
On Sat, Apr 18, 2015 at 10:37 AM, Shea Levy <sh...@shealevy.commailto:sh...@shealevy.com> wrote:
Yes, I just discovered that. Now I get a lot of errors like this building the resulting tarball:
pats_main_dats.o: In function _2nix_2tmp_2nix_2dbuild_2dATS2_2dPostiats_2etgz_2edrv_2d10_2ATS_2dPostiats_2src_2pats_main_2edats__staload': pats_main_dats.c:(.text+0x14af): undefined reference to ATS_2d0_2e2_2e12_2libc_2SATS_2stdio_2esats__staload’
There appear to be missing references to libc and libats functions, even though those are compiled.
cd ${PATSHOME}; make CBOOT
cd ${PATSHOME}/doc/DISTRIB; make atspackaging; make atspacktarzvcf
On Thursday, April 16, 2015 at 5:09:09 AM UTC-4, Shea Levy wrote:
Hi all,
How is the release tarball (that doesn’t require ATS 1 and just needs ./configure; make; make install) generated from the git sources? I’m poking around Makefile_devl now to try to build it in-tree but I’d like to know how to make a fake local release to test any changes I might want to make fully.