Tried to do a emerge aspell (0.33.7.1-r1) on two systems now but the compile stops with an error when making data. since this happend on two different systems I guess you will be able to reproduce it. If not I will provide more information later.
actually, it's been compiling for just about everybody, since I unmasked it a few weeks ago. So, please do provide me with an emerge log. I assume both machines are failing in the same place?
can you put a log in here please?
I can't build aspell (0.33.7.1-r1) either. Here is a log of what make outputs: make[2]: Entering directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1/data' cd ../; bd=`pwd`; cd scowl/final; \ cat english-*.10 english-*.20 english-*.35 english-*.50 \ english-*.60 english-*.65 \ special-*.35 special-*.50 \ | $bd/src/aspell --lang=english \ create master $bd/data/english-med-only cd ../; bd=`pwd`; cd scowl/final; \ cat american-*.10 american-*.20 american-*.35 american-*.50 \ american-*.60 american-*.65 \ | $bd/src/aspell --lang=english \ create master $bd/data/american-med-only cat: write error: Broken pipe make[2]: *** [english-med-only] Error 134 make[2]: *** Waiting for unfinished jobs.... cat: write error: Broken pipe make[2]: *** [american-med-only] Error 134 make[2]: Leaving directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1/data' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1' make: *** [all-recursive-am] Error 2 make all-recursive It's interesting. $bd/data/american-med-only does not exist (where $bd=/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1/). This may be why make reports a broken pipe. I checked the aspell bugs list, and they seem to think it's a binutils issue. Here's the link: http://sourceforge.net/tracker/index.php?func=detail&aid=511727&group_id=245&atid=100245 I'm not sure exactly why binutils would cause this behavior. By the way I'm running: gentoo: 1.2 binutils: 2.11.92.0.12.3-r2 glibc: 2.2.5-r5 gcc: 2.95.3-r7 linux: gentoo-sources-2.4.19-r7 What binutils, gcc, etc. are you running, Seemant? Let me know how/if I can help track this bug down. Arun
My problem is exactly the same as Arun's. !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 3287, Exitcode 2 !!! (no error message)
Please try aspell-0.33.7.1-r2 when it hits the rsync mirrors, its masked so you may have to unask it first.
r2 built flawlessly. I actually tried the fix listed on the aspell bugs page; it didn't work for me. That may be because I touched /etc/aspell.conf and not /etc/aspell/aspell.conf. I should have read the ebuild more carefully... Thanks, Dan.
Daniel, I'm glad you found a working solution. But, it is not the perfect one, unfortunately. Firstly, the ebuild touching anything in /root is bad, and against policy. Secondly, if this is packaged as a tbz2 file, then the /etc/aspell stuff -- will that exist? (I haven't looked closely enough, so I dunno). However, if you can find a way to circumvent this (like maybe have the aspell compile process look into ${D} or create a ${WORKDIR}/working directory and point it there instead, that would be much preferable... Thanks
Seemant, I agree, the solution is far from pretty. The problem when building in a gcc 2.95.3 and glibc-2.2.5 is that the built aspell checks for /etc/aspell/aspell.conf and /root/.aspell when it initally compiles the wordlists. This is, according to the bug report on aspell's sourceforge page only specific to gcc 2.95.3 and glibc-2.2.5. I havent looked into patching the source to remove the checks, but since the same code works in diffrent environments I can only assume that the bug lies somewhere else. I will have another look at this tomorrow at work. I'm not sure what you mean by packaing as a .bz2 file.
Daniel, no, I meant tbz2 package -- binary package. I think aspell's install process creates an /etc/aspell in ${D}, so it's probably a moot point anyway. Either way touching /etc directly goes against gentoo policy, and touching /root is probably intrusive.
I managed to compile aspell with the rc2, but I did not manage to do any spell checking with it (it just printed Aborting! when I did a aspell check foo.txt) I tried to create a ebuild for aspell-no (norwegian support), so this might be the problem...also /etc/aspell/aspell.conf was a zero size file. Did it work ok after installation on other systems? I got one more gentoo system here that I will try to build aspell on and I will check how it works there.
I got the same error on the second system. I unasked the r2 and did a emerge aspell Created /tmp/foo.txt and did a aspell check /tmp/foo.txt The only message I got was Aborting
Created attachment 2570 [details] strace output for aspell run Yea, I have the same problem. I didn't have a chance to try the aspell build until now. It seems that /etc/aspell/aspell.conf and /root/.aspell.conf are empty. That could be a problem. Here's the tail of what strace gives: stat64("/root/.aspell.english.pws", 0xbff921cc) = -1 ENOENT (No such file or directory) access("/root/.aspell.english.pws", F_OK) = -1 ENOENT (No such file or directory) open("/root/.aspell.english.per", O_RDONLY) = -1 ENOENT (No such file or directory) brk(0x80a9000) = 0x80a9000 rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0 getpid() = 6204 kill(6204, SIGABRT) = 0 --- SIGABRT (Aborted) --- +++ killed by SIGABRT +++ I assume that the fact that these files don't exist is why aspell aborts. I have attached the full trace. There are a few other errors in the trace. I don't think they're significant though. I shall investigate some more...
I tried touching /root/.aspell.english.pws and /root/.aspell.english.per, but no luck. I guess that's not the problem. I'll keep looking.
Same problem here: make[2]: Entering directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1/data' cd ../; bd=`pwd`; cd scowl/final; \ cat english-*.10 english-*.20 english-*.35 english-*.50 \ english-*.60 english-*.65 \ special-*.35 special-*.50 \ | $bd/src/aspell --lang=english \ create master $bd/data/english-med-only cd ../; bd=`pwd`; cd scowl/final; \ cat american-*.10 american-*.20 american-*.35 american-*.50 \ american-*.60 american-*.65 \ | $bd/src/aspell --lang=english \ create master $bd/data/american-med-only cat: write error: Broken pipe make[2]: *** [american-med-only] Error 134 make[2]: *** Waiting for unfinished jobs.... cat: write error: Broken pipe make[2]: *** [english-med-only] Error 134 make[2]: Leaving directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1/data' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1' make: *** [all-recursive-am] Error 2 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 3587, Exitcode 2 !!! (no error message)
I have the same problem here too: creating aspell make[2]: Leaving directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1/src' Making all in data make[2]: Entering directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1/data' cd ../; bd=`pwd`; cd scowl/final; \ cat english-*.10 english-*.20 english-*.35 english-*.50 \ english-*.60 english-*.65 \ special-*.35 special-*.50 \ | $bd/src/aspell --lang=english \ create master $bd/data/english-med-only cd ../; bd=`pwd`; cd scowl/final; \ cat american-*.10 american-*.20 american-*.35 american-*.50 \ american-*.60 american-*.65 \ | $bd/src/aspell --lang=english \ create master $bd/data/american-med-only cat: write error: Broken pipe make[2]: *** [american-med-only] Error 134 make[2]: *** Waiting for unfinished jobs.... cat: write error: Broken pipe make[2]: *** [english-med-only] Error 134 make[2]: Leaving directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1/data' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/aspell-0.33.7.1-r1/work/aspell-.33.7.1' make: *** [all-recursive-am] Error 2 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 3587, Exitcode 2 !!! (no error message) !!! emerge aborting on /usr/portage/app-text/aspell/aspell-0.33.7.1-r1.ebuild .
I also have difficulties with aspell : r1 didn't build. r2 built but don't work : nothing but "Abandon" message although I've created a $HOME/.aspell.conf using the 'aspell dump config' output and I copied $HOME/.aspell.fr.pws and $HOME/.aspell.fr.prepl from a box on which aspell works. On this box, there are no $HOME/.aspell.conf nor /etc/aspell/ So, it doesn't seem to come from config files. The box on which aspell works is a Debian and the aspell version is .33.7.1 alpha. May be should we try with other compilation options ?
i have the same problem. very annoying since a few packages have aspell in their dependency list (sylpheed-claws being one of them).
I suggest you guys/gals check out the aspell 0.50 pre-release ebuilds. It worked for me. The pre-release may not work with the applications that you are trying to use it with though. There are some significant changes in this release. Btw, the final aspell 0.50 is slated to be released in a week.
*** Bug 6773 has been marked as a duplicate of this bug. ***
The problem with aspell 0.50 pre-release, is that the dictionnaries ebuilds don't merge any more : word-list-compress d < fr-40-only.cwl | aspell --lang=fr create master ./fr-40-only.rws word-list-compress d < fr-60-only.cwl | aspell --lang=fr create master ./fr-60-only.rws Error: Unknown Action: create Error: Unknown Action: create make: *** [fr-40-only.rws] Error 1 make: *** Waiting for unfinished jobs.... make: *** [fr-60-only.rws] Error 1 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 2, Exitcode 2 !!! (no error message) !!! emerge aborting on /usr/portage/app-i18n/aspell-fr/aspell-fr-0.1.3.ebuild . I think it is because, now, to create dictionnary, speller-util should be used instead of aspell. And the previous created dictionnary don't work any more with aspell 0.50 : $ aspell check doc/cv/cv.tex Unhandled Error: The file "/usr/lib/aspell/fr-40-only.rws" is not in the proper format. Abandon
ok, I thought I added some dictionaries. Either way, by the end of the weekend the entire set of dictionaries for aspell-0.50* will be in portage. Please note, everyone, that the versions of the dictionaries will be 0.0.10.0 or 0.1.10.0 etc. In other words, if it's higher than 0.1, you don't want it. So, you have to explicitly emerge that version, which in many cases aspell-{fr,es,de,da} will be the lower versions in those categories.
right lads, aspell-0.50 is now in portage -- this is the newest stable release. Additionally the aspell-en, aspell-{en,es,de,fr,nl} dictionaries are updated for it. Please check the package.mask file. With the exception of the aspell-de, they are all the highest versions for the dictionaries. Test away!
Aspell-import supposedly can be used to import old dictionaries. I haven't used it though. Perhaps, we should include this functionality in the ebuild?
Arun, I've made a note in the pkg_postinst which gets spammed to the user about aspell-import. I think it has to be done on a per-user basis, because it imports the personal dictionaries. I think it is a little buggy too...
Oh, ok. Makes sense.
I wanted to tell that a-spell, aspell-en & aspell-nl just build fine for me (gcc 3.2, ix86) Thought you may wanted to know before releasing everything... Regards, Rigo
I emerged aspell-en (and therefore aspell 0.50) and gnome-spell under gcc 2.95.3. It emerged well, and I have spellchecking under evolution again! OTOH, pspell emerged well but pspell-ispell wouldn't.
Joe, the new aspell does not have a pspell-ispell module. That is something that they are planning to obsolete at some point. Everyone, aspell-0.50 is looking really good. The only roadbump which prevents me from unmasking it is abiword, which for some retarded reason uses pspell-ispell. Upstream, they are not touching it to change it. So in the interim, if any of you are good at coding, please have a look at abiword's sources to see if they can be patched to use the new aspell instead. I also have one of our own developers looking into it, but if anyone has insight that would be cool! Thanks
the new aspell-0.50.1 has been released and unmasked. it will even accept your optimisation settings.