Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> I didn't invoke automake myself, I was just disclosing the toolset.
> Does it get fired off by autoreconf?
It provides some of the macros used in generating the configure
script.
___
Guile-user mailing list
Gu
On Thu, 25 Jan 2007, Kevin Ryde wrote:
> Hugh Sasse <[EMAIL PROTECTED]> writes:
> >
> > automake (GNU automake) 1.9.6
>
> You might have to check where it's .m4 macros are installed. If
> they're not in a known place you can run
I didn't invoke automake myself, I was just disclosing the toolset
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> automake (GNU automake) 1.9.6
You might have to check where it's .m4 macros are installed. If
they're not in a known place you can run
aclocal -I /my/automake/dir/share/aclocal
or wherever.
You might not have to run aclocal, but I've never kno
On Tue, 23 Jan 2007, Kevin Ryde wrote:
> Hugh Sasse <[EMAIL PROTECTED]> writes:
> >
> > I'm stumped. And sun's native patch implementation chokes on this.
>
> Should have been ok. Change the lines manually, or checkout the cvs
> "branch_release-1-8" if you're brave.
bash-2.05$ cvs -z3 -d:pserv
On Tue, 23 Jan 2007, Kevin Ryde wrote:
> Hugh Sasse <[EMAIL PROTECTED]> writes:
> >
> > mov 0, %o1
> > callprintf, 0
>
> Ah dear, thanks, gcc has optimized it out. I'll change the test
> program to something like
>
> #include
> volatile double x = 0.0;
>
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> mov 0, %o1
> callprintf, 0
Ah dear, thanks, gcc has optimized it out. I'll change the test
program to something like
#include
volatile double x = 0.0;
int main () { return (isinf(x) != 0); }
probably add
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> I'm stumped. And sun's native patch implementation chokes on this.
Should have been ok. Change the lines manually, or checkout the cvs
"branch_release-1-8" if you're brave.
___
Guile-user mailing list
Guile-
On Mon, 22 Jan 2007, Kevin Ryde wrote:
> I made this change:
>
bash-2.05$ /bin/rm -rf guile-1.8.1
bash-2.05$ gtar -zxf guile-1.8.1.tar.gz
bash-2.05$ cd guile-1.8.1
bash-2.05$ gpatch < ../guile-configure.in.echo-n.diff
patching file configure.in
Hunk #1 FAILED at 27.
1 out of 1 hunk FAILED -- sav
On Mon, 22 Jan 2007, Kevin Ryde wrote:
> Hugh Sasse <[EMAIL PROTECTED]> writes:
> >
> >> You might be able to stick something in to save the conftest.c used.
> >
> > Possibly. I'm not familiar enough with autoconf to be confident about
> > that.
>
> Oh, what I meant was if you edit the generated
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
>> You might be able to stick something in to save the conftest.c used.
>
> Possibly. I'm not familiar enough with autoconf to be confident about
> that.
Oh, what I meant was if you edit the generated configure to do a cp of
conftest.c at the right spot.
I made this change:
--- configure.in.~1.268.2.28.~ 2006-12-27 10:32:04.0 +1100
+++ configure.in 2007-01-22 10:03:13.0 +1100
@@ -27,8 +27,15 @@
AC_PREREQ(2.53)
-AC_INIT(m4_esyscmd(. ./GUILE-VERSION && echo -n ${PACKAGE}),
-m4_esyscmd(. ./GUILE-VERSION && echo -n ${GUILE
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> -AC_INIT(m4_esyscmd(. ./GUILE-VERSION && echo -n ${PACKAGE}),
> -m4_esyscmd(. ./GUILE-VERSION && echo -n ${GUILE_VERSION}))
> +define(GUILE_PACKAGE_NAME,m4_esyscmd(. ./GUILE-VERSION && ${ECHO_N}
> ${PACKAGE}))
> +define(GUILE_PACKAGE_VERSION,m4_es
On Fri, 19 Jan 2007, Kevin Ryde wrote:
> Hugh Sasse <[EMAIL PROTECTED]> writes:
> > autoreconf -if
> > (with autoconf 2.61) I get a vastly different configure script
> > with spurious "-n"s sprinkled throughout:
> >
> > bash-2.05$ gdiff -u configure{.orig,} | head -20
> > --- configure.orig
On Fri, 19 Jan 2007, Kevin Ryde wrote:
> Hugh Sasse <[EMAIL PROTECTED]> writes:
> >
> > ./.libs/libguile.so: undefined reference to `isinf'
> >
> > At which point I am now stuck. After all, configure found isinf.
>
> You might be able to stick something in to save the conftest.c used.
Possibly.
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> ./.libs/libguile.so: undefined reference to `isinf'
>
> At which point I am now stuck. After all, configure found isinf.
You might be able to stick something in to save the conftest.c used.
Or maybe it's no more than
#include
int main (
I have managed to get a relatively successful build:
gmake check-TESTS
gmake[4]: Entering directory
`/export/home/Scratch/hgs/guile-1.8.1/test-suite/standalone'
PASS: test-system-cmds
PASS: test-require-extension
PASS: test-num2integral
PASS: test-round
PASS: test-gh
PASS: test-asmobs
PASS: test
Hi,
Kevin Ryde <[EMAIL PROTECTED]> writes:
> An alternative would be the gnulib portable implementations of all
> these bits, which do some explict manipulation of the "environ" global
> variable.
Yes, I think `gnulib' could make our lives easier in a number of
areas...
Thanks,
Ludovic.
_
On Thu, 18 Jan 2007, Kevin Ryde wrote:
> Hugh Sasse <[EMAIL PROTECTED]> writes:
> >
> > putenv putenv (3c) - change or add value to environment
> >
> > The manual page says it should be of the form "name=value" and the
> > string should not be automatic. In a function it should be dec
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> putenv putenv (3c) - change or add value to environment
>
> The manual page says it should be of the form "name=value" and the
> string should not be automatic. In a function it should be declared
> static.
Yep. I believe there's a bit of va
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> That rather depends on for whom they are developing. Aguments in
> "Brave Gnu World" about software use in the third world where download
> speeds are still limited,
Yep, such as Australia. The theory as I see it though is that there's
barely a dozen d
On Tue, 16 Jan 2007, Hugh Sasse wrote:
> On Tue, 16 Jan 2007, Kevin Ryde wrote:
>
> > Hugh Sasse <[EMAIL PROTECTED]> writes:
> > >
> > > posix.c: In function 'scm_putenv':
> > > posix.c:1332: error: 'len' undeclared (first use in this function)
> >
> > Thanks. Dodgy conditionals :-(. You can u
On Tue, 16 Jan 2007, Kevin Ryde wrote:
> Hugh Sasse <[EMAIL PROTECTED]> writes:
> >
> > posix.c: In function 'scm_putenv':
> > posix.c:1332: error: 'len' undeclared (first use in this function)
>
> Thanks. Dodgy conditionals :-(. You can use the "len" at the start
> of the function (claiming to
On Tue, 16 Jan 2007, Kevin Ryde wrote:
> Hugh Sasse <[EMAIL PROTECTED]> writes:
> >
> > On Sat, 13 Jan 2007, Kevin Ryde wrote:
> >
> >> Otherwise if you think there's a function but no prototype we could
> >> put a prototype in (when not otherwise provided).
> >
> > that sounds like the best appro
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> posix.c: In function 'scm_putenv':
> posix.c:1332: error: 'len' undeclared (first use in this function)
Thanks. Dodgy conditionals :-(. You can use the "len" at the start
of the function (claiming to be for mingw).
Does that mean there's no unsetenv()
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> On Sat, 13 Jan 2007, Kevin Ryde wrote:
>
>> Otherwise if you think there's a function but no prototype we could
>> put a prototype in (when not otherwise provided).
>
> that sounds like the best approach to me. There is a definition to
> be picked up whe
On Mon, 15 Jan 2007, Hugh Sasse wrote:
> On Sat, 13 Jan 2007, Kevin Ryde wrote:
>
> > You might be able to just stick in a prototype,
>
> Tried to do that, it still complained about it.
> > or alternately just
> > "./configure --disable-error-on-wa
On Sat, 13 Jan 2007, Kevin Ryde wrote:
> Hugh Sasse <[EMAIL PROTECTED]> writes:
> >
> >> cc1: warnings being treated as errors
>
> That's designed to force all users to be developers :-(.
Should that be in the *release* then? Prior to release definitely
makes sense.
>
> >> numbers.c: In funct
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
>> cc1: warnings being treated as errors
That's designed to force all users to be developers :-(.
>> numbers.c: In function 'xisinf':
>> numbers.c:147: warning: implicit declaration of function 'isinf'
You might be able to just stick in a prototype, or al
On Fri, 5 Jan 2007, Hugh Sasse wrote:
> I am now getting :
>
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -D_REENTRANT -pthreads -g -O2
> -Wall -Wmissing-prototypes -Werror -MT libguile_la-numbers.lo -MD -MP -MF
> .deps/libguile_la-numbers.Tpo -c numbers.c -fPIC -DPIC -o
> .libs/libguile_la-
I am now getting :
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -D_REENTRANT -pthreads -g -O2 -Wall
-Wmissing-prototypes -Werror -MT libguile_la-numbers.lo -MD -MP -MF
.deps/libguile_la-numbers.Tpo -c numbers.c -fPIC -DPIC -o
.libs/libguile_la-numbers.o
cc1: warnings being treated as errors
num
30 matches
Mail list logo
