Hi Ryan,
We would like to find out why latest version of emacs21 (21.4+1-2) failed to
build
on mipsel.
21.4+1-1 used to build fine and no change related to the C code nor autoconf
files has been made in 21.4+1-2.
Since we don't have a clean sid chroot on vaughan (the only developer mipsel
machi
Le jeudi 21 décembre 2006 21:34, Rob Browning a écrit :
> Jérôme Marant <[EMAIL PROTECTED]> writes:
>
> > Rob, are you taking care of this, or should I?
>
> Please do, if you have the time.
I will only available till next Saturday so I guess someone will have to
take care of it if both of us are
Jérôme Marant <[EMAIL PROTECTED]> writes:
> Rob, are you taking care of this, or should I?
Please do, if you have the time.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Le samedi 16 décembre 2006 21:09, Rob Browning a écrit :
> Jérôme Marant <[EMAIL PROTECTED]> writes:
>
> > Shall we contact Ryan?
>
> Sounds like a good idea. Though I suppose there's another difference
> between vaughan and the buildd. On vaughan I wasn't building from a
> clean chroot.
Rob,
Jérôme Marant <[EMAIL PROTECTED]> writes:
> Shall we contact Ryan?
Sounds like a good idea. Though I suppose there's another difference
between vaughan and the buildd. On vaughan I wasn't building from a
clean chroot.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexa
Le samedi 16 décembre 2006 19:08, Rob Browning a écrit :
> Jérôme Marant <[EMAIL PROTECTED]> writes:
>
> > It looks like it has been rescheduled for building yesterday and it
> > is still failing.
> >
> > Please note that vaughan is not the build machine. It is "rem" which
> > is maitained by Ryan
Jérôme Marant <[EMAIL PROTECTED]> writes:
> It looks like it has been rescheduled for building yesterday and it
> is still failing.
>
> Please note that vaughan is not the build machine. It is "rem" which
> is maitained by Ryan Murray.
Right, but it is a mipsel machine, so the fact that it works
Le samedi 16 décembre 2006 04:18, Rob Browning a écrit :
> [EMAIL PROTECTED] writes:
>
> > Do you know how to use an etch chroot on vaughan? (I guess this is the
> > only mipsel machine available to developers?)
> >
> > Thanks in advance.
>
> I just started a build in the vaughan sid chroot, and
[EMAIL PROTECTED] writes:
> Do you know how to use an etch chroot on vaughan? (I guess this is the
> only mipsel machine available to developers?)
>
> Thanks in advance.
I just started a build in the vaughan sid chroot, and it's well past
sysdep.c now, so I'm not sure what the problem is, but I'm
Andreas Barth <[EMAIL PROTECTED]> writes:
> mipsel-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -DUSE_LUCID
> -I. -I/build/buildd/emacs21-21.4a+1/src -D_BSD_SOURCE -DDEBIAN -g -O2
> -DPURESIZE=500 -I../src /build/buildd/emacs21-21.4a+1/src/sysdep.c
> /build/buildd/emacs21-21.4a+
* Andreas Barth <[EMAIL PROTECTED]> [2006-12-15 16:52]:
> > No, fails in the same way.
> "Same way" as on the buildd, I assume?
Yeah.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
* Martin Michlmayr ([EMAIL PROTECTED]) [061215 15:56]:
> * Martin Michlmayr <[EMAIL PROTECTED]> [2006-12-15 15:28]:
> > Okay, it works after removing autoconf2.13. Let's see whether the
> > package compiles...
>
> No, fails in the same way.
"Same way" as on the buildd, I assume?
Cheers,
Andi
-
Le vendredi 15 décembre 2006 16:45, Martin Michlmayr a écrit :
> * Jérôme Marant <[EMAIL PROTECTED]> [2006-12-15 16:08]:
> > Then I don't know. Why does it fail only on mipsel?
> > As I said no patch has been applied to the C code nor anything related
> > to it (like autotools).
> >
> > Dare I que
* Jérôme Marant <[EMAIL PROTECTED]> [2006-12-15 16:08]:
> Then I don't know. Why does it fail only on mipsel?
> As I said no patch has been applied to the C code nor anything related
> to it (like autotools).
>
> Dare I question the toolchain?
I don't know.
--
Martin Michlmayr
http://www.cyrius.
* Martin Michlmayr <[EMAIL PROTECTED]> [2006-12-15 15:28]:
> Okay, it works after removing autoconf2.13. Let's see whether the
> package compiles...
No, fails in the same way.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscri
Le vendredi 15 décembre 2006 15:56, Martin Michlmayr a écrit :
> * Martin Michlmayr <[EMAIL PROTECTED]> [2006-12-15 15:28]:
> > Okay, it works after removing autoconf2.13. Let's see whether the
> > package compiles...
>
> No, fails in the same way.
Then I don't know. Why does it fail only on mip
* Martin Michlmayr <[EMAIL PROTECTED]> [2006-12-15 15:19]:
> * Stephen Gran <[EMAIL PROTECTED]> [2006-12-15 14:10]:
> > > autoconf 2.60a-4 and autoconf2.13 2.13-58 are installed on my machine.
> > Which one does /usr/bin/autoconf point to?
>
> autoconf --version
> Autoconf version 2.13
Okay, it w
Le vendredi 15 décembre 2006 15:22, Stephen Gran a écrit :
> This one time, at band camp, Martin Michlmayr said:
> > * Stephen Gran <[EMAIL PROTECTED]> [2006-12-15 14:10]:
> > > > autoconf 2.60a-4 and autoconf2.13 2.13-58 are installed on my machine.
> > > Which one does /usr/bin/autoconf point to?
* Stephen Gran <[EMAIL PROTECTED]> [2006-12-15 14:10]:
> > autoconf 2.60a-4 and autoconf2.13 2.13-58 are installed on my machine.
> Which one does /usr/bin/autoconf point to?
autoconf --version
Autoconf version 2.13
---
Autoconf 2.13 chosen by Debian wrapper script.
--
Martin Michlmayr
http://ww
This one time, at band camp, Martin Michlmayr said:
> * Stephen Gran <[EMAIL PROTECTED]> [2006-12-15 14:10]:
> > > autoconf 2.60a-4 and autoconf2.13 2.13-58 are installed on my machine.
> > Which one does /usr/bin/autoconf point to?
>
> autoconf --version
> Autoconf version 2.13
> ---
> Autoconf 2
This one time, at band camp, Martin Michlmayr said:
> * Jérôme Marant <[EMAIL PROTECTED]> [2006-12-15 14:41]:
> > > Any hint which one that could be? What auto* do you use yourself?
> > Those macros are part of autoconf.
>
> autoconf 2.60a-4 and autoconf2.13 2.13-58 are installed on my machine.
W
* Jérôme Marant <[EMAIL PROTECTED]> [2006-12-15 14:41]:
> > Any hint which one that could be? What auto* do you use yourself?
> Those macros are part of autoconf.
autoconf 2.60a-4 and autoconf2.13 2.13-58 are installed on my machine.
--
Martin Michlmayr
http://www.cyrius.com/
Le vendredi 15 décembre 2006 14:38, Andreas Barth a écrit :
> > > autoconf: Undefined macros:
> > > configure.in:1351:AC_SYS_LARGEFILE
> > > configure.in:1442:AC_C_PROTOTYPES
> > > configure.in:1443:AC_C_VOLATILE
> > > configure.in:2040:AC_FUNC_MKTIME
> > > configure.in:2047:AC_FUNC_FSEEKO
> > > c
* Jérôme Marant ([EMAIL PROTECTED]) [061215 13:43]:
> Le vendredi 15 décembre 2006 12:52, Martin Michlmayr a écrit :
> > fakeroot debian/rules autofiles-sync gives:
> >
> > ...
> > test "$(QUILT_PATCHES=debian/patches quilt top)" = autofiles.diff
> > QUILT_PATCHES=debian/patches quilt pop
> > Remo
Le vendredi 15 décembre 2006 12:52, Martin Michlmayr a écrit :
> fakeroot debian/rules autofiles-sync gives:
>
> ...
> test "$(QUILT_PATCHES=debian/patches quilt top)" = autofiles.diff
> QUILT_PATCHES=debian/patches quilt pop
> Removing patch autofiles.diff
> Restoring aclocal.m4
> Restoring confi
fakeroot debian/rules autofiles-sync gives:
...
test "$(QUILT_PATCHES=debian/patches quilt top)" = autofiles.diff
QUILT_PATCHES=debian/patches quilt pop
Removing patch autofiles.diff
Restoring aclocal.m4
Restoring configure
Now at patch ldapsearch-output.diff
mkdir -p debian/tmp-autofiles/old
tar
* Jérôme Marant ([EMAIL PROTECTED]) [061215 11:35]:
> Le mardi 12 décembre 2006 16:46, Andreas Barth a écrit :
>
> >
> > As described in the developers reference:
> > http://www.debian.org/doc/developers-reference/ch-resources.en.html#s-dchroot
> >
> > However, apt sources don't seem to be too c
Le mardi 12 décembre 2006 16:46, Andreas Barth a écrit :
>
> As described in the developers reference:
> http://www.debian.org/doc/developers-reference/ch-resources.en.html#s-dchroot
>
> However, apt sources don't seem to be too current there. If there is
> anything I can help you on "my" mipsel
Le vendredi 15 décembre 2006 11:38, Andreas Barth a écrit :
> * Jérôme Marant ([EMAIL PROTECTED]) [061215 11:35]:
> > Le mardi 12 décembre 2006 16:46, Andreas Barth a écrit :
> >
> > >
> > > As described in the developers reference:
> > > http://www.debian.org/doc/developers-reference/ch-resource
Le mardi 12 décembre 2006 16:46, Andreas Barth a écrit :
> As described in the developers reference:
> http://www.debian.org/doc/developers-reference/ch-resources.en.html#s-dchroot
>
> However, apt sources don't seem to be too current there. If there is
> anything I can help you on "my" mipsel-ma
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) [061212 15:43]:
> Selon Andreas Barth <[EMAIL PROTECTED]>:
>
> > * Jérôme Marant ([EMAIL PROTECTED]) [061212 13:31]:
> > > Le jeudi 07 décembre 2006 02:20, Rob Browning a écrit :
> > >
> > > > I suppose it's possible that that changing the series order might
Selon Andreas Barth <[EMAIL PROTECTED]>:
> * Jérôme Marant ([EMAIL PROTECTED]) [061212 13:31]:
> > Le jeudi 07 décembre 2006 02:20, Rob Browning a écrit :
> >
> > > I suppose it's possible that that changing the series order might have
> > > broken something if I didn't re-run "autofiles-sync" aft
* Jérôme Marant ([EMAIL PROTECTED]) [061212 13:31]:
> Le jeudi 07 décembre 2006 02:20, Rob Browning a écrit :
>
> > I suppose it's possible that that changing the series order might have
> > broken something if I didn't re-run "autofiles-sync" after the move,
> > but I thought I did.
>
> Hi Rob,
Le jeudi 07 décembre 2006 02:20, Rob Browning a écrit :
> I suppose it's possible that that changing the series order might have
> broken something if I didn't re-run "autofiles-sync" after the move,
> but I thought I did.
Hi Rob,
Are you working on it ?
--
Jérôme Marant
Jérôme Marant <[EMAIL PROTECTED]> writes:
> Didn't you break the autofiles, by chance? You told me you changed
> something in the autodiff patch?
I only moved the autofiles.diff back to the end of patches/series. It
had migrated to be next to last, and it has to be last.
One way to make sure th
Le mardi 05 décembre 2006 10:18, Andreas Barth a écrit :
> Package: emacs21
> Version: 21.4a+1-2
> Severity: serious
>
> Hi,
>
> the build of emacs failed on mipsel. Please see
> http://buildd.debian.org/fetch.cgi?&pkg=emacs21&ver=21.4a%2B1-2&arch=mipsel&stamp=1165216366&file=log
> for the full b
Le mardi 05 décembre 2006 10:18, Andreas Barth a écrit :
> Package: emacs21
> Version: 21.4a+1-2
> Severity: serious
>
> Hi,
>
> the build of emacs failed on mipsel. Please see
> http://buildd.debian.org/fetch.cgi?&pkg=emacs21&ver=21.4a%2B1-2&arch=mipsel&stamp=1165216366&file=log
> for the full b
Package: emacs21
Version: 21.4a+1-2
Severity: serious
Hi,
the build of emacs failed on mipsel. Please see
http://buildd.debian.org/fetch.cgi?&pkg=emacs21&ver=21.4a%2B1-2&arch=mipsel&stamp=1165216366&file=log
for the full build log.
Toolchain package versions: libc6-dev_2.3.6.ds1-7 linux-kernel-h
38 matches
Mail list logo
