Redhat 6.1 was used to build the 1.2.2 source, later releases of gcc
refused to even compile the assembler files, and you need to remove the
comment lines if you are using a later release. One of the challenges
with developing on linux is how fast distributions change, the tools
all changed in a year.
If you are seeing segfaults then I would suggest using the patched
motif from openmotif.org, you need the development tree version.
rt.jar is a release bundle, for development you can just use the classes
in the build/classes directory.
regards
calvin
Brian Craft wrote:
>
> (resending this, since the server seems to eat messages unless you're
> subscribed)
>
> ----- Forwarded message from Brian Craft <[EMAIL PROTECTED]> -----
>
> Hey -- I got the Sun source, for jdk1.2.2, but the build is horribly
> broken. It spits out invalid assembler code, among other things.
>
> With a bit of fussing (removing bogus assembler comments), I got it
> to build, but the resulting binaries are not the same as the blackdown
> 1.2.2 binaries, and they segfault regularly.
>
> I didn't find any diff on blackdown for 1.2.2.
>
> What's the deal? How do you build this stuff?
>
> Alternately, does anyone know if there's a way to replace the
> existing awt class w/o rebuilding the tool chain? From what I
> can tell, awt is built into libawt, and rt.jar refers to it
> somehow. Maybe I can just rebuild rt.jar? Anyone know how?
>
> Also note that the build info in the FAQ doesn't work, since sun
> isn't serving the 1.2 source, and the blackdown docs don't work
> for 1.2.2. In particular, the patches won't apply to the 1.2.2
> source.
>
> b.c.
>
> ----- End forwarded message -----
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
