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] |
RakeshN <rakeshn@kpit.com> wrote: > CC must be set to working compiler. In the Canadian cross scenario, before you build your host x target toolchain, you must first build and install a build x host and a build x target toolchain. > I searched for i586-cygwin32-gcc and found out the path for this gcc.=20 > > I then set CC to that gcc and exported it. No, this is the wrong way to do it. (It is the right way for GNU packages, but not for the Cygnus tree.) Your i586-cygwin32-gcc must be in your PATH. The Cygnus configure will set CC, CC_FOR_TARGET, and CC_FOR_BUILD correctly for each module given correct --build, --host, and --target options. Don't try to set them manually, in the Cygnus tree it's way too complicated! -- Michael Sokolov Harhan Engineering Laboratory Public Service Agent International Free Computing Task Force International Engineering and Science Task Force 615 N GOOD LATIMER EXPY STE #4 DALLAS TX 75204-5852 USA Phone: +1-214-824-7693 (Harhan Eng Lab office) E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP) (UUCP coming soon) P.S. See /pub/embedded/cygnus-tree-intro on ivan.Harhan.ORG for more information on the Cygnus tree. ------ 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] |