* Hakan Ardo ([EMAIL PROTECTED]) wrote: > On Sun, Jan 13, 2002 at 04:01:45PM +0000, Dr. David Alan Gilbert wrote: > > > > summary > > ------- > > All binutils seem to build happily > > Gcc's are a lot more of a problem > > Nice going!
No problem. > > associated stuff; is it appropriate to use dpkg-cross to get these? > > I don't know what's the best solution here. What is the procedure proposed > upstream? A variety of nasty hacks, half working solutions which work some of the time for some combinations of source and destination with some compiler versions. My suggestion is to use dpkg-cross to get appropriate libraries and point to the place it installs them, perhaps even make the dpkg-cross installed packages included in the build dependencies. (Anyone know of an apt-get hack for dpkg-cross so it can get and install all dependents in the cross chain?) > > Is it intended that I use > > > > tpkg-make alpha-linux > > > > or should I be using > > > > tpkg-make alpha > > This one "tpkg-make alpha" -linux will be added in the rules file. I'll add > this to the README as well. Or shall we change it? Personally I'd prefer that the name is passed-as-is to the gcc/binutils configures; because I normally know what to give those to get what I want. I'd agree with adding the -linux in if it was for everything, but since this package has the ability to build for things Linux won't run on (e.g. AVR - anyone fancy a small port....) I'd rather not do it conditionally. Dave ---------------- Have a happy GNU millennium! ---------------------- / Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \ \ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex / \ _________________________|_____ http://www.treblig.org |_______/