This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I am interested in the MIPS. I have cross compiled gcc 3.4.1, glibc 2.3.2 and binutils 2.15. (Posted the patches for this to the mailing list, still owe you a patch for kernel 2.4.18 to work with gcc 4.x.) This is what I want to generate a rpm for. Personally, I liked it much better when you just specified -buildrpm and it would generate the rpm for whatever you were compiling. I am curious why did you move away from this to the buildrpm.sh scripts?? On Tue, 2005-06-07 at 11:58 -0700, Daniel Kegel wrote: > Marc Karasek wrote: > > I noticed that the -buildrpm option in crosstools is no longer there. I > > took a look at the buildrpm.sh script and am a bit confused as to how to > > use this to build for a cross toolchain. I do not see where you specify > > the target processor. > > The buildrpm.sh script in crosstool-0.35 is just: > > TOOLCOMBOS="gcc-3.4.3-glibc-2.2.2" > export TOOLCOMBOS > sh crosstool-0.35/buildsrpms.sh > mkdir -p result > for toolcombo in $TOOLCOMBOS; do > cp rpmbuild/SRPMS/crosstool-$toolcombo*.src.rpm result > rpm -i result/crosstool-$toolcombo*.src.rpm > rpmbuild -bb rpmbuild/SPECS/crosstool-$toolcombo*.spec --without all --with i686 > cp rpmbuild/RPMS/*/crosstool-$toolcombo*.rpm result > done > > The important parameters are > rpmbuild ... --without all --with i686 > > Remove --without all --with i686 and rpmbuild will build toolchains > for all known working cpu types. buildsrpms.sh looks in buildlogs > to see which ones work. > > Or leave the --without all, and give --with your-favorite-cpu-type. > > (Well, there's a problem with powerpc-foo > toolchains, for which a patch was recently contributed; I can > dig that up if you need it.) > > What CPUs are you interested in? > - Dan -- Any content within this email is provided âAS ISâ for informational purposes only. No contract will be formed between the parties by virtue of this email. /*********************** Marc Karasek System Lead Technical Engineer iVivity Inc. T 678-990-1550 x238 F 678-990-1551 ***********************/ ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |