> No, its enough to rebuild the package with the new gcc package pointing > to gcc-4.1 installed.
Sure, but relying on (build-essential + libgcj-dev) assumes that the gcc and gcj versions will always be the same. Past experience has suggested this is not the case, which is why I've leaned towards java-gcj-compat-dev instead. b. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]