| 1 |
Hi all, |
| 2 |
|
| 3 |
I was upgrading gcc using the directions in the GCC Upgrade Guide. All |
| 4 |
was going well. I was user what the Guide refers to as the "safer" |
| 5 |
method. I got to the 321 of 642 mark and the upgrade bombed. |
| 6 |
|
| 7 |
The specific upgrade being done was cyrus-sasl. Early in the output it |
| 8 |
complained about both "gdbm" and "berkdb" USE flags being set. Then, a |
| 9 |
message was displayed that it would be best to build this package with |
| 10 |
berkdb and told me how to set this in my "package.use" file. The build |
| 11 |
waited 10 seconds and then proceeded. This occurred overnight, so I'm |
| 12 |
just finding this out. |
| 13 |
|
| 14 |
Immediately after waiting the 10 seconds for a response to the db issue, |
| 15 |
the build process displayed this message: |
| 16 |
|
| 17 |
* If you are still using postfix->sasl->saslauthd->pam->mysql for |
| 18 |
* authentication, please edit /etc/conf.d/saslauthd to read: |
| 19 |
* SASLAUTHD_OPTS="${SASLAUTH_MECH} -a pam -r" |
| 20 |
* Don't forget to restart the service: `/etc/init.d/saslauthd restart`. |
| 21 |
|
| 22 |
I'm not exactly sure what this means. I do have mysql on my system and |
| 23 |
have to provide a password when I use the database associated with it, |
| 24 |
but beyond that, I don't know if I should be doing what this message is |
| 25 |
telling me or not. Assistance here would be appreciated. |
| 26 |
|
| 27 |
Again, a pause for 10 seconds occurred while waiting for a response, but |
| 28 |
since I was asleep and didn't give one, the build went ahead. |
| 29 |
|
| 30 |
The configure process completed and the make started. |
| 31 |
|
| 32 |
The last few lines before the make process bombed and the first couple |
| 33 |
of lines of the error message are as follows: |
| 34 |
|
| 35 |
ar cru .libs/libsasldb.a db_gdbm.o allockey.o |
| 36 |
ar: allockey.o: No such file or directorymake[2]: *** [libsasldb.a] Error 1 |
| 37 |
make[2]: *** [libsasldb.a] Error 1 |
| 38 |
make[2]: Leaving directory |
| 39 |
`/var/tmp/portage/cyrus-sasl-2.1.20/work/cyrus-sasl-2.1.20/sasldb' |
| 40 |
|
| 41 |
If I am interpreting this correctly, it the configure and build went |
| 42 |
ahead using gdbm rather than berkdb and the correction would be to edit |
| 43 |
my package.use file as previously indicated and rebuild. |
| 44 |
|
| 45 |
However, my issue is that since I was at the 321/642 point of doing the |
| 46 |
'emerge -e' world' portion of the upgrade, I don't know how to rectify |
| 47 |
the problems and continue with the upgrade. Or do I have to start from |
| 48 |
scratch with the 'emerge -e world'? |
| 49 |
|
| 50 |
Can someone offer some guidance here? |
| 51 |
|
| 52 |
I apologize for the length of this, but wanted to make sure that I |
| 53 |
included all the details that might be relevant. |
| 54 |
|
| 55 |
Regards, |
| 56 |
|
| 57 |
Colleen |
| 58 |
|
| 59 |
|
| 60 |
|
| 61 |
-- |
| 62 |
gentoo-user@g.o mailing list |
Archives