From mboxrd@z Thu Jan 1 00:00:00 1970 From: JAY LULLA To: crossgcc@sourceware.cygnus.com, gcc-help@gcc.gnu.org Cc: jay.lulla@ebay.sun.com, hsing.yuan@ebay.sun.com, swamin@ebay.sun.com Subject: Installing cross-compiler for PowerPC 603, pSOS Date: Fri, 14 Jan 2000 11:35:00 -0000 Message-id: <387F7A4E.85093CF7@Sun.COM> X-SW-Source: 2000-01/msg00131.html Hi. I would like to get some advice about cross-compiling GCC for a Sun Solaris host, and PowerPC target. We have already installed gcc-2.95.2, with its complete source. Here are some issues I need to address: - should the cross-compiler be installed in the same dir as the native compiler, and then be called with a special flag, or should it be installed in a whole new directory altogether? - should we use flags such as 'with-as' 'with-ld' and 'with-headers' to specify directories for the assembler, linker, and headers, or is it best to leave these out, and then specify which assemblers, linkers etc to use as flags when we actually use the cross-gcc? - If we use the flags when we actually run gcc, we would have more flexibility in trying different assemblers and linkers, or have the option of not linking at all, right? - Or would you have the same flexibility by installing it with default directories, and then overriding the defaults if you choose to do so when running gcc? - does it matter what version of 'make' one uses? ie whether we use 'make' from cc or from GNU? - I've never used binutils before. What is it all about? Does it have any useful tools for profiling the code (analyzing it to produce a function call graph, for example)? ----------------------------- On a related note, I notice that GCC has tools to make it compatible with certain embedded operating systems. Are there any tools for pSOS? I couldn't find any... Thanks, Jay Lulla jay.lulla@ebay.sun.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: JAY LULLA To: crossgcc@sourceware.cygnus.com, gcc-help@gcc.gnu.org Cc: jay.lulla@ebay.sun.com, hsing.yuan@ebay.sun.com, swamin@ebay.sun.com Subject: Installing cross-compiler for PowerPC 603, pSOS Date: Sat, 01 Apr 2000 00:00:00 -0000 Message-ID: <387F7A4E.85093CF7@Sun.COM> X-SW-Source: 2000-q1/msg00131.html Message-ID: <20000401000000.M56_fwzA6f7-atsD7W00QIIZvJeukQFDbuayHUML_SI@z> Hi. I would like to get some advice about cross-compiling GCC for a Sun Solaris host, and PowerPC target. We have already installed gcc-2.95.2, with its complete source. Here are some issues I need to address: - should the cross-compiler be installed in the same dir as the native compiler, and then be called with a special flag, or should it be installed in a whole new directory altogether? - should we use flags such as 'with-as' 'with-ld' and 'with-headers' to specify directories for the assembler, linker, and headers, or is it best to leave these out, and then specify which assemblers, linkers etc to use as flags when we actually use the cross-gcc? - If we use the flags when we actually run gcc, we would have more flexibility in trying different assemblers and linkers, or have the option of not linking at all, right? - Or would you have the same flexibility by installing it with default directories, and then overriding the defaults if you choose to do so when running gcc? - does it matter what version of 'make' one uses? ie whether we use 'make' from cc or from GNU? - I've never used binutils before. What is it all about? Does it have any useful tools for profiling the code (analyzing it to produce a function call graph, for example)? ----------------------------- On a related note, I notice that GCC has tools to make it compatible with certain embedded operating systems. Are there any tools for pSOS? I couldn't find any... Thanks, Jay Lulla jay.lulla@ebay.sun.com