yeah , all fixed , it was autotools being too strict , and interpreting  dense 
code as not posix compliant code , I just added a few newlines (to find out 
which bit it thought was non-posix ) and the problem went away :)



On Tuesday 25 May 2010 21:01:35 Bill Hart wrote:
> I think the setversion script actually runs autoreconf, from memory.
> If your version of autotools is different (which it is) this will
> essentially screw it up for boxen.
>
> Anyhow, it seems you have it under control now.
>
> On 25 May 2010 20:55, Jason Moxham <ja...@njkfrudils.plus.com> wrote:
> > On Tuesday 25 May 2010 20:51:42 Bill Hart wrote:
> >> Hmm. I don't know about the first error, but the second is easy to
> >> resolve by doing:
> >>
> >> automake --add-missing
> >>
> >> The final one can safely be ignored.
> >>
> >> I personally think it is a bad idea to rely on a machine of an
> >> individual that others don't have access to, to manage autotools
> >> stuff. It is much, much better to just resolve any issues on boxen.
> >
> > I agree , we were just lazy :)
> >
> >> Bill.
> >>
> >> On 25 May 2010 20:46, Jason Moxham <ja...@njkfrudils.plus.com> wrote:
> >> > On Tuesday 25 May 2010 20:33:32 Minh Nguyen wrote:
> >> >> Hi Jason,
> >> >>
> >> >> On Tue, May 25, 2010 at 12:33 PM, Jason Moxham
> >> >> <ja...@njkfrudils.plus.com> wrote:
> >> >>
> >> >> <SNIP>
> >> >>
> >> >> > yes , although as we have the new msvc files in I think we going to
> >> >> > call it 2.1.0
> >> >>
> >> >> <SNIP>
> >> >>
> >> >> > according to these rules
> >> >> > http://sources.redhat.com/autobook/autobook/autobook_91.html
> >> >> >
> >> >> > as we have added a new function mpn_sqr  we must increment current
> >> >> > , set rev to 0 , and increment age so we 10.0.1  and 4.8.1
> >> >>
> >> >> Thank you very much for the clarification. After checking out trunk
> >> >> on boxen.math, I edited the script setversion as per your suggestion.
> >> >> To update the versioning of MPIR, I ran the modified script
> >> >> setversion, only to receive the following error from autotools:
> >> >>
> >> >> [mv...@boxen mpir-2.1.0]$ pwd
> >> >> /dev/shm/mvngu/mpir-2.1.0
> >> >> [mv...@boxen mpir-2.1.0]$ svn update
> >> >> At revision 2962.
> >> >> [mv...@boxen mpir-2.1.0]$ ./setversion
> >> >> Setting MPIR to
> >> >> MPIR-2.1.0
> >> >> GMP-soname-10.0.1
> >> >> GMPXX-soname-4.8.1
> >> >> autoreconf: configure.ac: AM_GNU_GETTEXT is used, but not
> >> >> AM_GNU_GETTEXT_VERSION configure.in: required file `./ylwrap' not
> >> >> found configure.in:   `automake --add-missing' can install `ylwrap'
> >> >> Makefile.am:412: echo -e "\n": non-POSIX variable name
> >> >> Makefile.am:412: (probably a GNU make extension)
> >> >> autoreconf: automake failed with exit status: 1
> >> >>
> >> >> Do you or anyone have any ideas what going on?
> >> >
> >> > yeah , the autotools on boxen is a newer one than what we are used to
> >> > , we havent got around to updating Makefile.am to get rid of the
> >> > non-posix bit. I can run it on mine , to make the dist , and upload it
> >> > to boxen , or I can fix the script , or perhaps we can launch
> >> > autotools is a less pedantic mode
> >> >
> >> >> --
> >> >> Regards
> >> >> Minh Van Nguyen
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google
> >> > Groups "mpir-devel" group. To post to this group, send email to
> >> > mpir-de...@googlegroups.com. To unsubscribe from this group, send
> >> > email to mpir-devel+unsubscr...@googlegroups.com. For more options,
> >> > visit this group at http://groups.google.com/group/mpir-devel?hl=en.
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "mpir-devel" group. To post to this group, send email to
> > mpir-de...@googlegroups.com. To unsubscribe from this group, send email
> > to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this
> > group at http://groups.google.com/group/mpir-devel?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to mpir-de...@googlegroups.com.
To unsubscribe from this group, send email to 
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en.

Reply via email to