From mboxrd@z Thu Jan 1 00:00:00 1970 From: rich-paul@rich-paul.net To: "Martin v. Loewis" Cc: rich-paul@rich-paul.net, egcs@egcs.cygnus.com Subject: Re: Building binutils, egcs, gdb, etc Date: Fri, 30 Apr 1999 23:15:00 -0000 Message-ID: References: <199904012148.XAA14922@mira.isdn.cs.tu-berlin.de> X-SW-Source: 1999-04n/msg00019.html Message-ID: <19990430231500.49NTtfDe4ZgqNrx0mscQeP0v-XYAiNXo2Y5Zyv48aNA@z> I found one referance that said that this would happen if 'the sources were properly unpacked into the same directory' but have never seen any description of how one would do that. Takin for discussion just binutils and egcs, which configure script should be used? Which libiberty ( they differ ) Which libbfd? Perhaps this is a work in progress? --- There is a party that | Libertarian Party | A victimless crime is supports the right to | http://www.lp.org | a contradiction in free speach and | The Party of | terms. encryption!! | Principal | On Thu, 1 Apr 1999, Martin v. Loewis wrote: > > I built binutils, egcs, and gdb ( Versions 2.9.1, 1.1.2, and 4.17 > > respectively). > > > > Here is the issue: Each of these packages want to build and install > > their own versions of libiberty and bfd, and gdb wants to use a > > private libreadline, rather than the one that I had already > > installed and used for bash. > > I believe the standard approach is to put all packages into the same > source directory. Cygnus configure will look what sources are there, > and build everything. Then, all the packages will share libiberty and > libbfd. > > Hope this helps, > Martin >