This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hi, Russ.Shaw wrote: > When compiling gcc for an embedded cpu, and newlib > is required, is "with-headers" needed as an option > to "configure gcc" ? > > Does this mean newlib should be installed before > gcc? > > Does the "with-headers" option need to point to > a directory? > > Should newlib be installed before binutils? > > Are there other ways of including newlib > when compiling the whole system? This means you should have newlib unpacked for making the compiler. You can't make the newlib without having a compiler, but the compiler needs to know, what will be in the newlib once it's done (for libgcc I believe). Normally it goes the following way. make binutils unpack newlib unpack gcc configure gcc (--with-headers=<path to the newlib-headers>) make gcc configure and make newlib. Regards, Stefan. -- ----------------------------------------------------------------------- Dipl.-Ing. Stefan M. Petters http://www.rcs.ei.tum.de Institute for Real-Time Computersystems (RCS) fon +49/89-289-23556 Technische Universitaet Muenchen, D-80290 Muenchen fax +49/89-289-23555 ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |