| Summary: | g77 problem in gcc-3.2.3-r1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jianghai Zhu <zhu5> |
| Component: | Current packages | Assignee: | George Shapovalov (RETIRED) <george> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | major | CC: | gcc-porting |
| Priority: | Highest | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 18933 | ||
| Bug Blocks: | |||
| Attachments: |
g77 version
g77 version g77 version |
||
|
Description
Jianghai Zhu
2003-09-02 18:11:18 UTC
Created attachment 18143 [details]
g77 version
the g77 version is still 3.2.2 when I upgrade gcc to 3.2.3-r1. becasue the
version of g77 and gcc don't match, it caused all those fortan compiler related
problems. Everything works fine when I downgrade my gcc to 3.2.2-r2.
Created attachment 18144 [details]
g77 version
the g77 version is still 3.2.2 when I upgrade gcc to 3.2.3-r1. becasue the
version of g77 and gcc don't match, it caused all those fortan compiler related
problems. Everything works fine when I downgrade my gcc to 3.2.2-r2.
Created attachment 18145 [details]
g77 version
the g77 version is still 3.2.2 when I upgrade gcc to 3.2.3-r1. becasue the
version of g77 and gcc don't match, it caused all those fortan compiler related
problems. Everything works fine when I downgrade my gcc to 3.2.2-r2.
Hi Jianghai. Sorry for the delay, recent bugzilla change left me with 100+ open bugs. which I am sorting through now.. However I am (still) quite puzzled by the report: how did you end up with the setup you are describing? Just to make sure: we are talking about the g77 that is part of gcc, right? That one is just bundled and gets installed or updated with every new version. Did you by chance do anything strange with gcc-config? However it is supposed to anly switch between 2.95 and 3.x series - it is not that trivial to keep the system in a consistent state alternating between 3.2 and 3.3... Could you have been bitten by a problemmatic gcc ebuild? Although the uninstall should have removed old g77 version, did you set AUTOCLEAN to no? Ok, the only reasonable thing I see is to try to remedy your situation. I see you downgraded gcc, which solved the problem. This is a good forst step which, I suspect, is necessary not only for fortran - looks like your gcc setup was screwed. Now, if you want to upgrade, I would suggest to enable AUTOCLEAN and perform preferably full rebuild of your system (looks like this can be done "live" in your case - just launch "emerge -pe system" in the background..). You might switch to gcc-3.3 along the way, or perform this clean-up when it becomes stable. During switch to gcc-3.3 similar rebuild isrecommended anyway, because gcc people (again) slightly broke ABI compatibility :(. As I said, if you prefer stable tree, you might want to waint until gcc-3.3 becomes stable, - some helper scripts might be released then and more packages will be gcc-3.3 "compliant". Please let me know, if you still have this problem. If these measures do not solve it to you I will probably reassign this bug to gcc people, as this seems to be gcc issue, rhather than fortran-specific. Georg This bug has been inactive for 90 days or more. gcc is currently at 3.2.3-r3 for x86. Is this still a problem? Please reopen this bug if it is still relevant. With Gentoo Linux 2004.0 using GCC 3.3.2-r5, the bug is still present! Creating a symlink to include f771 (in "/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2") in PATH made the error message disappear, but left me with a "ld: cannot find -lg2c" message. However, running g77 instead of f77 seems to get the job done, but this meant I had to edit the install-script of the application (DaliLite) I wanted to compile... Almost forgot: GCC was recompiled 'USE="f77" emerge gcc'! |
