some problems when using gcc3.0 instead of gcc2.95.3

Cliff Tsai
Tue Jun 26 21:07:00 GMT 2001


    I've build gcc3.0 for ARM under cygwin.
    But a lot of similar error occurs:
    /Include/mylib.h:100:20: warning: no newline at end of file

    But all the codes work fine when using gcc2.95.3,why?

    And what "__EH_FRAME_BEGIN__" and "__EH_FRAME_END__"  mean?
    I don't see them when using gcc2.95.3.
    My solution is PROVIDE a un-used address for them in the linker script!
    I don't know if there exist side-effect!



Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

More information about the crossgcc mailing list