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]

testing newer toolchain components


  even though my sh3 build seems to work, if i wanted to test newer
toolchain components and i have some machine cycles to spare, is there
anything untoward about just bumping up a component version number and
letting it build?

  for example, sh3 has the combination:

	gcc-3.4.1
	glibc-2.3.3
	binutils-2.15

just for fun, i could bump gcc up to 3.4.2 or 3.4.3 and see what
happens?  is there a rigorous recipe for doing this kind of testing,
or does one just crank up the version number(s) and let it rip to see
what happens?

rday

p.s.  obviously, i'd make all appropriate changes to the .dat files.

------
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]