[Bug 246406] Re: FTBFS in Intrepid. No mode in open call

2009-06-13 Thread Bug Watch Updater
** Changed in: yap (Debian) Status: New => Fix Released -- FTBFS in Intrepid. No mode in open call https://bugs.launchpad.net/bugs/246406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lis

[Bug 246406] Re: FTBFS in Intrepid. No mode in open call

2009-06-04 Thread Bug Watch Updater
** Changed in: yap (Debian) Status: Unknown => New -- FTBFS in Intrepid. No mode in open call https://bugs.launchpad.net/bugs/246406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ub

[Bug 246406] Re: FTBFS in Intrepid. No mode in open call

2009-06-03 Thread Michael Terry
** Bug watch added: Debian Bug tracker #531744 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531744 ** Also affects: yap (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531744 Importance: Unknown Status: Unknown -- FTBFS in Intrepid. No mode in open call https://

[Bug 246406] Re: FTBFS in Intrepid. No mode in open call

2008-09-21 Thread Luca Falavigna
Erm... I uploaded 5.1.1-3ubuntu1 without noticing your bug report... sorry :( yap (5.1.1-3ubuntu1) intrepid; urgency=low * debian/patches/04_ubuntu_toolchain_FTBFS.dpatch: - Fix FTBFS with current Ubuntu toolchain. * debian/rules: - Compile with -fno-stack-protector on i386, fix FTBFS

[Bug 246406] Re: FTBFS in Intrepid. No mode in open call

2008-07-08 Thread Bobby R. Ward
The include problem was fixed but then I ran into the stack check problems. I added -fno-stack-protector to CFLAGS to get around this for now. I'm not sure of a better way to fix this or where the problem truly lies. ** Attachment added: "yap_5.1.1-3ubuntu1.debdiff" http://launchpadlibrarian.

[Bug 246406] Re: FTBFS in Intrepid. No mode in open call

2008-07-08 Thread Michael Bienia
Looks like there is a include missing: x86_64-linux-gnu-gcc -c -g -O2 -DCOROUTINING=1 -DRATIONAL_TREES=1 -DDEPTH_LIMIT=1 -DHAVE_CONFIG_H -I. -I../H -I../OPTYap -I../BEAM -I../MYDDAS ../C/alloc.c -o alloc.o ../C/alloc.c: In function 'ExtendWorkSpace': ../C/alloc.c:912: error: 'S_IRUSR' undeclare

[Bug 246406] Re: FTBFS in Intrepid. No mode in open call

2008-07-08 Thread Bobby R. Ward
Thanks for looking at it. Forgot about the comments in the patch. ** Attachment added: "yap_5.1.1-3ubuntu1.debdiff" http://launchpadlibrarian.net/15889462/yap_5.1.1-3ubuntu1.debdiff -- FTBFS in Intrepid. No mode in open call https://bugs.launchpad.net/bugs/246406 You received this bug notifi

[Bug 246406] Re: FTBFS in Intrepid. No mode in open call

2008-07-08 Thread Cesare Tirabassi
Looks good to me. I would just fill in the required info in the dpatch header: ## 04_open-mode.dpatch by <[EMAIL PROTECTED]> ## ## All lines beginning with `## DP:' are a description of the patch. ## DP: No description. instead of <[EMAIL PROTECTED]> there should be your email. Note that if you

[Bug 246406] Re: FTBFS in Intrepid. No mode in open call

2008-07-07 Thread Bobby R. Ward
** Attachment added: "yap_5.1.1-3ubuntu1.debdiff" http://launchpadlibrarian.net/15877971/yap_5.1.1-3ubuntu1.debdiff -- FTBFS in Intrepid. No mode in open call https://bugs.launchpad.net/bugs/246406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 246406] Re: FTBFS in Intrepid. No mode in open call

2008-07-07 Thread Bobby R. Ward
** Attachment added: "buildlog_ubuntu-intrepid-i386.yap_5.1.1-3_FAILEDTOBUILD.txt.gz" http://launchpadlibrarian.net/15877969/buildlog_ubuntu-intrepid-i386.yap_5.1.1-3_FAILEDTOBUILD.txt.gz -- FTBFS in Intrepid. No mode in open call https://bugs.launchpad.net/bugs/246406 You received this bug