When gcc-3.2.2 was installed the LDPATH parameter in the file /etc/env.d/05env still contained the information for gcc-3.2.1. The LDPATH parameter pended the new information infront delimited by a colon. This caused gedit to fail to compile. Reproducible: Always Steps to Reproduce: 1.This was originally an RC_2 install so YMMV 2. 3. Expected Results: Probably upon the unmerge the old gcc-3.2.1 info should have been removed from the /etc/env.d/05env file.
Dang, can't reed, rite or spel. In the problem description please substitute 05env for 05gcc. Thanks!
Works fine here. When did you merge gcc-3.2.2 ?
The RC_2 Stage 1 system was built February 9. The gcc-3.2.1 was either built or rebuilt on February 14, gcc-3.2.2 was built February 24. I only found the problem when gedit wouldn't build, it was still looking for the old /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1 because the /etc/ld.so.conf file still had both paths in it because the /etc/env.d/05gcc LDPATH parameter looked like this: LDPATH="/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2:/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1" That isn't something that happens accidentally that happens programatically.
Right. Had some issues back at that stage, but they should be fixed now. Please remerge gcc-3.2.2, or run: # gcc-config i686-pc-linux-gnu-3.2.2 Like I said, after March 20, this should be fixed.
