I have exaimed the config.log file from the bad build and found that libesmtp is looking for gcc-3.X In the log, the is s -std=c99 set for tests. Since gcc-2.95.x does not understand the c99 standard, configure fails. If I add to the ebuild --disable-isoc, which disables c99 standards checking, the program compiles, but fails to install with an unlink error. Yet, I can manually type in the unlink command from a su'd root console window and the unlink command works. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: compiled fine. This bug is stopping the system from updating all the packages in a emerge -u world If you need me to do anything, or send anything, let me know.
Sorry, our e-mail server decided to commit suicide. It should be back up by the time I've commit this comment.
Could you paste the output from emerge info and the output from configure and the build.
Daniel; Would you like the config.log, eclass-debug.log and the environment files. emerge is building it correctly. If not, I can pipe the emerge build into a file to attach here. BTW, my email is still down. The admin stated that all should be resolved this evening. [That's what we have been hearing for the last couple of days :-( ]
Created attachment 11733 [details] New ebuild for libesmtp I have resolved the problems with building under gcc-2.95 There are some compile warnings that I plan on working on. But, the attached tar.gz file has the new ebuild, ChangeLog and digest files.
Created attachment 11734 [details] New ebuild for libesmtp I have resolved the problems with building under gcc-2.95 There are some compile warnings that I plan on working on. But, the attached tar.gz file has the new ebuild, ChangeLog and digest files.
Commited, thanks for finding this!
