You are not logged in.
I'm playing around with building my own gcc based on the ABS supplied PKGBUILD file for gcc.
In the PKGBUILD file there is some comments about making a backwards compatible libc++.
To do so, it looks like the PKGBUILD first compiles gcc.3.3.3 and deletes everything but the libc++ and then rebuilds gcc 3.4.0.
Why is this neccesary? I
Offline
Because of the gcc build system. Go ahead, see if you can find another way to do it. Judd's already looked. If you do, feel free to share with everyone else by submitting a bug report.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
I think you misunderstood my question.
Why is there a need for a backward compatible libc++? I understand the comment about having to build the whole gcc in order to get the libc++.
Is there some arch linux packages that rely on an older libc++?
Offline
You weren't around when we upgraded openssl were you?
If we didn't include that lib, all C++ apps would have to be rebuilt. That's a lot of downloading for every single person.
Instead we opted to make the transition a little bit smoother.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
No I guess I wasn't around.
I figured that was the reason.
Offline