* GCC & binutils & ?
@ 2001-12-07 0:30 Dan Premetz
2001-12-07 4:05 ` Frank Schafer
2001-12-07 4:33 ` Andrea 'Fyre Wyzard' Bocci
0 siblings, 2 replies; 3+ messages in thread
From: Dan Premetz @ 2001-12-07 0:30 UTC (permalink / raw)
To: gcc-help
We use over 10 different compiler sets at work. One builds on IRIX for
IRIX, another builds on Solaris for Solaris, several are cross-compilers for
embedded systems, etc. When we build, we pretty much do the same thing
regardless of which compiler we're using:
1.) We compile source code to object files (gcc, g++)
2.) We create libs (ar)
3.) We link everything together to get executables (ld)
I expected that GCC had everything I needed to do the above. I guess this
is not the case. What all do I need if I want to do items (1), (2), and
(3)? I think I'm looking at GCC and binutils, right? Is there anything
else which would be of interest to someone doing C/C++ software development?
-DLP
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: GCC & binutils & ?
2001-12-07 0:30 GCC & binutils & ? Dan Premetz
@ 2001-12-07 4:05 ` Frank Schafer
2001-12-07 4:33 ` Andrea 'Fyre Wyzard' Bocci
1 sibling, 0 replies; 3+ messages in thread
From: Frank Schafer @ 2001-12-07 4:05 UTC (permalink / raw)
To: Dan Premetz; +Cc: gcc-help
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
Dan Premetz wrote:
> We use over 10 different compiler sets at work. One builds on IRIX for
> IRIX, another builds on Solaris for Solaris, several are cross-compilers for
> embedded systems, etc. When we build, we pretty much do the same thing
> regardless of which compiler we're using:
>
> 1.) We compile source code to object files (gcc, g++)
> 2.) We create libs (ar)
> 3.) We link everything together to get executables (ld)
>
> I expected that GCC had everything I needed to do the above. I guess this
> is not the case. What all do I need if I want to do items (1), (2), and
> (3)? I think I'm looking at GCC and binutils, right? Is there anything
> else which would be of interest to someone doing C/C++ software development?
>
> -DLP
Hi Dan,
there is a lot of INTERESTING stuff ( of course ;o), but gcc and binutils is
sufficient for the tasks you mentioned.
Frank
[-- Attachment #2: Card for Frank Schafer --]
[-- Type: text/x-vcard, Size: 218 bytes --]
begin:vcard
n:Schafer;Frank
x-mozilla-html:FALSE
org:SETUZA a.s.;IT
adr:;;;;;;
version:2.1
email;internet:frank.schafer@setuza.cz
title:Dipl. Ing.
note:System administrator
x-mozilla-cpt:;0
fn:Frank Schafer
end:vcard
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: GCC & binutils & ?
2001-12-07 0:30 GCC & binutils & ? Dan Premetz
2001-12-07 4:05 ` Frank Schafer
@ 2001-12-07 4:33 ` Andrea 'Fyre Wyzard' Bocci
1 sibling, 0 replies; 3+ messages in thread
From: Andrea 'Fyre Wyzard' Bocci @ 2001-12-07 4:33 UTC (permalink / raw)
To: Dan Premetz, gcc-help
At 02.30 07/12/01 (GMT -0600), Dan Premetz wrote:
>We use over 10 different compiler sets at work. One builds on IRIX for
>IRIX, another builds on Solaris for Solaris, several are cross-compilers for
>embedded systems, etc.
You might need newlib when compiling for embedded systems.
> When we build, we pretty much do the same thing
>regardless of which compiler we're using:
>
> 1.) We compile source code to object files (gcc, g++)
> 2.) We create libs (ar)
> 3.) We link everything together to get executables (ld)
>
>I expected that GCC had everything I needed to do the above. I guess this
>is not the case. What all do I need if I want to do items (1), (2), and
>(3)? I think I'm looking at GCC and binutils, right? Is there anything
>else which would be of interest to someone doing C/C++ software development?
>
>-DLP
fwyzard
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-12-07 12:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-07 0:30 GCC & binutils & ? Dan Premetz
2001-12-07 4:05 ` Frank Schafer
2001-12-07 4:33 ` Andrea 'Fyre Wyzard' Bocci
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).