what i learned making a gcj cross-compile environment for target=i386-cygwin

Tom Tromey what i learned making a gcj cross-compile environment for target=i386-cygwin
  • Next message (by thread): what i learned making a gcj cross-compile environment fortarget=i386-cygwin
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  • >>>>> "Tony" == Tony Kimball <alk@pobox.com> writes:
    
    Tony> i finally decided to put the cross-compiler on the back burner until
    Tony> i've explored using the compiler on cygwin directly.
    Tony> i submitted the patches above to the cygwin mailing list.
    I haven't built a Linux-x-Cygwin toolchain in a long, long time (three
    years at least). I don't remember it being such a problem, but I had
    a unified tree and I didn't try to build libgcj. In fact libgcj
    didn't exist when I did it.
    I think the above is probably best. I imagine at the current moment
    it is easier to try to build natively on Cygwin than it is to do a
    cross, especially for libgcj. I haven't built any libgcj cross in a
    couple years, and even then it was to a relatively simple target (a
    MIPS port using newlib), not to another host.
    Tom
    


    More information about the Java mailing list

    AltStyle によって変換されたページ (->オリジナル) /