I unmasked and was attempting to test aspell-0.50_pre20020730. I am using default-x86-2.0 with gcc-3.2_pre. The first thing I noticed was the CXXFLAGS from make.conf were not being used. This was not a showstopper, but it isn't optimized like it could be. The next problem involved the new gcc-3.2 c++ ABI. Apparently this version of aspell doesn't like it. Attempts to compile the file modules/speller/phonet.cpp result in undeclared identifier errors: line 177: `toupper' undeclared line 270: `isdigit' undeclared This reeks of a missing header file or deprecated namespace reference. Not sure which one it is yet.
yes, it will NOT inherit your optimisations. They break the ebuild. All you can do is get over that bit. As for the compile breaks, try the new snapshot and report. And please don't make things "blocker"s unless they really do break the installation of the system. That applies not to masked packages :P
*** Bug 6265 has been marked as a duplicate of this bug. ***
Well I am over it, I was never "on it" in the first place. I didn't read the ebuild, so I guess that's my fault. However, I have run into quite a few ebuilds which were not fixed to use optimizations. So, I jumped the gun on that one. As for the status, I screwed up, because I was trying to set it to "major", not blocker. Guess I must of slipped up there as well. Oh well, it's not like I caused WWW III or anything... As for the new snapshot, the good news is that it compiles fine. However, parts of the install phase seem to fail, but not fatally. This causes portage to install an unusable aspell. Here are the problems [note: I unmerged the previous aspell prior to building this one so that I could test a "fresh" install]: 1)When libtool attempts to relink libaspell against libaspell-common, ld complains that it cannot find libaspell-common. However, libaspell-common was successfully installed. It appears that libtool is not having the temporary install dir path passed to -L when it attempts to relink. Because this happens, any libraries that attempt to relink in this package fail to do so. 2)After installing the manual, ebuild.sh complains that /...//usr/share/doc/aspell-0.50_pre20020811 doesn't exist. This would most likely be due to the fact that the installer puts docs in /...//usr/share/doc/aspell/. 3)Compared to the previous edition, there were quite a few less headers installed in /...//usr/include/... It just seems suspect, but I'm not totally sure. So that's what I observed. YMMV, but I ran through the process 4 times to be certain I wasn't missing anything.
I've made some fixes to the ebuild, so please rsync (whenever your mirror updates itself), and put it into a log so I can see these errors, please. there is something interesting about the new aspell. it is supposed to encompass both aspell and pspell, and you have to install a dictionary separately. When I did that, I got some weird behaviour. Sylpheed-claws, for instance, doesn't recognise the dictionary.
What revision/timestamp will will the header on the new ebuild be? Just so I know the mirror got it. As for the dictionaries, have you tried one of the dictionaries at: http://savannah.gnu.org/download/aspell/dicts-cvs/? Also, am I supposed to uninstall pspell? What about the pspell-ispell package? I guess I can answer these questions through experimentation. What bug number concerned the optimization errors? I was thinking about trying it out on the snapshot to see if it is still broken.
# $Header: /home/cvsroot/gentoo-x86/app-text/aspell/aspell-0.50_pre20020811.ebuild,v 1.2 2002/08/14 13:04:48 seemant Exp $ Also, I've put aspell-en in app-i18n, but it doesn't seem to work for me. The new aspell, btw, is a combination of pspell and aspell. So, you can remove pspell and pspell-ispell. That's the dict from gnu.org, btw, which I was referring to earlier. See what you make of it, until I hear from Mr. Atkinson
Created attachment 3072 [details] aspell.log This is the log transaction of the build and install. It has installed a little more this time around, but the relinking errors are still of some concern. Note also the inability to switch to the desired directory as previously stated.
nicholas, bear with me, but what happens if you uncomment the lines in the ebuild: inherit libtool and then in src_compile, the line: elibtoolize do you still get those linking errors?
Yes, that worked perfectly! Still one minor issue with the ebuild. I'm getting this upon installation: make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/var/tmp/portage/aspell-0.50_pre20020811/work/aspell-0.50-20020811' make[1]: Leaving directory `/var/tmp/portage/aspell-0.50_pre20020811/work/aspell-0.50-20020811' install: `man-text' is a directory gzip: /var/tmp/portage/aspell-0.50_pre20020811/image/usr/share/doc/aspell-0.50_pre20020811/text/man-text: No such file or directory strip: /var/tmp/portage/aspell-0.50_pre20020811/image/usr/lib/libaspell-common-0.50.so Just thought I'd point that out. Thanks!
I just tested aspell from the command line with the en dictionary, seems to work fine there. Perhaps there is a new way to interface it from external mail clients?
