Hi, The biggest issue I see with this is that some of the tools hard-code the tool's location in the built code. I found that I could not move the tools tree once it was built, since many shell scripts referred back to the original location.
One of the tools having this issue is Bison (see TRAFODION-1588 <https://issues.apache.org/jira/browse/TRAFODION-1588>). As far as I remember it's other tools as well, and they may not have a workaround like Bison does. You could try to tar up your $TOOLSDIR and untar it to a different place and see what happens. We could of course require that users of the prebuilt tools restore them to /opt/home/tools. Hans On Mon, Mar 7, 2016 at 6:21 PM, Gunnar Tapper <[email protected]> wrote: > I suspect that we'd have to host it where we host the log4c++ RPM for the > 1.3 version. But, it'd make setup a lot easier if it's possible. > > On Mon, Mar 7, 2016 at 7:14 PM, Liu, Ming (Ming) <[email protected]> > wrote: > > > +1 > > > > Really helpful if we have such a repository online, put everything in one > > place. Is github a good place for such a repository? > > > > Thanks, > > Ming > > > > > > -----邮件原件----- > > 发件人: Gunnar Tapper [mailto:[email protected]] > > 发送时间: 2016年3月8日 9:58 > > 收件人: [email protected] > > 主题: Pre Build Development Tools for Download > > > > Hi, > > > > The longest time of the Trafodion development setup is to download and > > build the required build tools. > > > > Could we pre build these tools, put into a tar ball, and then make them > > available for download to make the setup time much shorter? > > > > -- > > Thanks, > > > > Gunnar > > *If you think you can you can, if you think you can't you're right.* > > > > > > -- > Thanks, > > Gunnar > *If you think you can you can, if you think you can't you're right.* >
