Re: Addition to Chapter 12

Miguel Bazdresch wrote these words on 08/20/05 21:29 CST: > * Randy McMurchy <[EMAIL PROTECTED]> [2005-08-21 01:50]: >>I haven't forgotten about your suggestions, Miguel. I'll be doing some >>research about your suggestions and putting the stuff into the book. I >>was hoping others would contribute

Re: Addition to Chapter 12

* Randy McMurchy <[EMAIL PROTECTED]> [2005-08-21 01:50]: > I haven't forgotten about your suggestions, Miguel. I'll be doing some > research about your suggestions and putting the stuff into the book. I > was hoping others would contribute some more ideas, and I'd do it all > at once. That's good

Re: Addition to Chapter 12

Miguel Bazdresch wrote these words on 08/11/05 19:36 CST: > About suggestions for other packages: oprofile is a nice alternative to > valgrind: http://oprofile.sourceforge.net/news/ > > We might consider adding more RCS packages, since source control is a > basic developers' tool. We might add da

Re: Addition to Chapter 12

* Randy McMurchy <[EMAIL PROTECTED]> [2005-08-11 23:32]: FWIW, this is how I build some of these packages. I use makefiles, assume DEST, TMP, INS, SRC are appropriate directories. untar is a bash function that untars .gz or .bzip2 files. > Boost BOOST = boost-1.32 .PHONY : boost boost : P = boo

Re: Addition to Chapter 12

On 8/11/05, Randy McMurchy <[EMAIL PROTECTED]> wrote: > In the meantime here is the list of packages I'm mentioning so far. > Please feel free to add to or recommend removing from the list. > > Boost > DDD > cachecc1 > ccache > distcc > Euphoria > FFTW > GDB > GOB > gocache > GTK+/GNOME Language B

Re: Creating logs of builds (was - Re: Addition to Chapter 12)

Bruce Dubbs wrote: > Do you mean something like this? :) > Horrible! :-) Seriously, I'm sure it works for you, but everyone should roll their own (Here Richard seeks to dominate the world with his own opinion - as usual :). I see LFS as teaching people about UNIX and Linux, and BLFS as teac

Re: Creating logs of builds (was - Re: Addition to Chapter 12)

Archaic wrote: > On Wed, Aug 10, 2005 at 07:25:27AM +0100, Richard A Downing wrote: > >>My way now is never to type the commands directly, but create a >>scriptlet for each package built from a template that is essentially >>Bruce's script plus some checks. > > > And to take automation one step

Re: Addition to Chapter 12

Randy McMurchy wrote these words on 08/09/05 11:40 CST: > I'd like to propose a new section added to Chapter 12 - Programming. > > A section titled "Other Programming Tools" I have the section finished and will be committing it shortly. I'm too lazy to copy it up somewhere, so it will not be ava

Re: Creating logs of builds (was - Re: Addition to Chapter 12)

Bruce Dubbs wrote these words on 08/10/05 22:53 CST: [snip 435 lines of stuff about building LFS] At this point, might it be best to move this thread over to a different list? :-) -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.

Re: Creating logs of builds (was - Re: Addition to Chapter 12)

Archaic wrote: > On Wed, Aug 10, 2005 at 07:25:27AM +0100, Richard A Downing wrote: > >>My way now is never to type the commands directly, but create a >>scriptlet for each package built from a template that is essentially >>Bruce's script plus some checks. > > > And to take automation one step

Creating logs of builds (was - Re: Addition to Chapter 12)

Tushar Teredesai wrote: > On 8/9/05, David Fix <[EMAIL PROTECTED]> wrote: > >>Though I don't have an install.log file... Is that standard? >>(Aw crap, now I'm showing that I don't know how to create this file! :P) > > > See the last paragraph in >

RE: Addition to Chapter 12

On Tue, 9 Aug 2005, David Fix wrote: > > *!$%# ! (translate that as "nice catch, Randy" for those > > with sensitive > > eyes). Actually, it's libbfd, libopcodes, and libiberty. I hadn't > > spotted that in my logs. Fortunately, only static and > > libtool versions. > > Zounds! So since I inst

RE: Addition to Chapter 12

> Note that you can redirect to a file in *append* mode by using >> > instead of >. Example: Yeah, I'd known that stuff... :) I just thought that "make install" in most standard packages made this mysterious install.log file. *blush* Ah, sometimes my naivete (and spelling errors) shine through

Re: Addition to Chapter 12

David Fix wrote these words on 08/09/05 18:45 CST: > Awesome. :) Thank you both. :) I always like to see stuff as I > compile/install/whatever it, just so I can see it's still doing something. > ;) Thanks again, both of you! You're welcome! Note that you can redirect to a file in *append* m

RE: Addition to Chapter 12

> > See the last paragraph in > > > packing.html>. > > Tush's suggestion is good, however, if all you want to do is create > a log file without thousands of lines of stuff scrolling across your > screen just redirect the output usin

Re: Addition to Chapter 12

Tushar Teredesai wrote these words on 08/09/05 18:25 CST: > On 8/9/05, David Fix <[EMAIL PROTECTED]> wrote: > >>Though I don't have an install.log file... Is that standard? >>(Aw crap, now I'm showing that I don't know how to create this file! :P) > > See the last paragraph in >

Re: Addition to Chapter 12

On 8/9/05, David Fix <[EMAIL PROTECTED]> wrote: > > Though I don't have an install.log file... Is that standard? > (Aw crap, now I'm showing that I don't know how to create this file! :P) See the last paragraph in . --

RE: Addition to Chapter 12

> Static versions of the 3 libraries mentioned above are installed by > the Binutils package. I'm not sure what all else might have been > overwritten by installing GDB the way you did. Install GDB in a > private directory for a complete list of files that are installed, > or closely review your in

RE: Addition to Chapter 12

> or closely review your install.log file created during the GDB > installation (you do have one, right?). Um... Ah... Of course I do. If I hadn't deleted my gdb install directory. :P I guess I'll just reinstall binutils, or will it actually matter? Dave -- http://linuxfromscratch.o

Re: Addition to Chapter 12

David Fix wrote these words on 08/09/05 16:45 CST: >> Actually, it's libbfd, libopcodes, and libiberty. I hadn't >>spotted that in my logs. Fortunately, only static and >>libtool versions. > > Zounds! So since I installed gdb without cd'ing into the gdb directory > before doing a "make install"

RE: Addition to Chapter 12

> *!$%# ! (translate that as "nice catch, Randy" for those > with sensitive > eyes). Actually, it's libbfd, libopcodes, and libiberty. I hadn't > spotted that in my logs. Fortunately, only static and > libtool versions. Zounds! So since I installed gdb without cd'ing into the gdb directory b

Re: Addition to Chapter 12

On Tue, Aug 09, 2005 at 11:40:28AM -0500, Randy McMurchy wrote: > > What say the group? Groovy. BTW, just taking a quick peek at my buildscript for strace (I can't remember how long it was that I wrote it), strace is a cmmi package. -- Archaic Want control, education, and security from your op

Re: Addition to Chapter 12

Ken Moffat wrote these words on 08/09/05 14:57 CST: > On Tue, 9 Aug 2005, Randy McMurchy wrote: > >>Or am I wrong about this and it is nothing more than CMMI? > > *!$%# ! (translate that as "nice catch, Randy" for those with sensitive > eyes). Actually, it's libbfd, libopcodes, and libiberty. I

Re: Addition to Chapter 12

On Tue, 9 Aug 2005, Randy McMurchy wrote: > > I don't install it using configure-make-make install. I use the > following: > > configure > make > make check-gdb > cd gdb > make install > > Notice the 'cd gdb' before 'make install'. This is how my build script > is laid out, and though my memory is

Re: Addition to Chapter 12

On 8/9/05, David Fix <[EMAIL PROTECTED]> wrote: > > Notice the 'cd gdb' before 'make install'. This is how my build script > > is laid out, and though my memory is fuzzy about this, I 'cd gdb' so > > that the readline, libiberty, etc. libraries aren't installed along > > with the gdb executable. >

Re: Addition to Chapter 12

David Fix wrote these words on 08/09/05 14:04 CST: > First off, what's CMMI? :D configure && make && make install > Secondly, I didn't do the "cd gdb" before I did > the "make install"... Is that going to cause me any problems? I don't remember. I know that I was paranoid that GDB may copy t

Re: Addition to Chapter 12

On Tue, Aug 09, 2005 at 03:04:36PM -0400, David Fix wrote: > > First off, what's CMMI? :D Secondly, I didn't do the "cd gdb" before I did CMMI: Centre for Molecular Microbiology and Infection or maybe, Capability Maturity Model Integration but I'm pretty sure in this instance Randy means Config

RE: Addition to Chapter 12

> Notice the 'cd gdb' before 'make install'. This is how my build script > is laid out, and though my memory is fuzzy about this, I 'cd gdb' so > that the readline, libiberty, etc. libraries aren't installed along > with the gdb executable. > > Or am I wrong about this and it is nothing more than

Re: Addition to Chapter 12

Randy McMurchy wrote these words on 08/09/05 13:32 CST: > And so forth and so on as I think of (and y'all provide) more ideas > to include on this page. These items will also be included: Numeric (python numerical extension) Boost FFTW GOB GTK bindings SWIG Valgrind More ideas are welcome! --

Re: Addition to Chapter 12

Randy McMurchy wrote: And so forth and so on as I think of (and y'all provide) more ideas to include on this page. 'ddd' I believe is the preferred (read stable & currently well-maintained) GUI frontend for gdb. Homepage: http://www.gnu.org/software/ddd/ Download URL: http://ftp.gnu.org/gnu

Re: Addition to Chapter 12

Bruce Dubbs wrote these words on 08/09/05 12:01 CST: > This is a reasonable thing to do. It would also act as a TODO list as > we can then transistion the links to full install pages in the same > chapter as time allows. Here is the lead-in paragraph for the new section. Please comment. "This s

Re: Addition to Chapter 12

Randy McMurchy wrote: > Hi all, > > I'd like to propose a new section added to Chapter 12 - Programming. > > A section titled "Other Programming Tools" > > In this section would be nothing but links to the home pages for various > other programming tools such as Strace and GDB. > > Granted, mos

Re: Addition to Chapter 12

Randy McMurchy wrote: > > In BLFSspeak, section = page. Right. Thanks. ;) -- JH -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page

Re: Addition to Chapter 12

Jeremy Huntwork wrote these words on 08/09/05 11:46 CST: > It sounds alright, but if you're only providing links and not build > instructions, do you really need an entirely new section? Wouldn't one > page suffice? In BLFSspeak, section = page. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20

Re: Addition to Chapter 12

David Fix wrote these words on 08/09/05 11:45 CST: > Definitely. :) I was quite surprised to find that there was no GDB in BLFS > whatsoever... :) I mean, yeah, I can easily download, build, and install > it, but for people who may not know where to find it... Great idea. :) Which bring me

Re: Addition to Chapter 12

Jeremy Huntwork wrote: > Randy McMurchy wrote: >> What say the group? > > It sounds alright, but if you're only providing links and not build > instructions, do you really need an entirely new section? Wouldn't one > page suffice? Just re-read your original comment - I see that I might have misund

Re: Addition to Chapter 12

Randy McMurchy wrote: I'd like to propose a new section added to Chapter 12 - Programming. A section titled "Other Programming Tools" In this section would be nothing but links to the home pages for various other programming tools such as Strace and GDB. Sounds good. Justin -- http://linu

Re: Addition to Chapter 12

Randy McMurchy wrote: > What say the group? It sounds alright, but if you're only providing links and not build instructions, do you really need an entirely new section? Wouldn't one page suffice? -- JH -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.or

RE: Addition to Chapter 12

> In this section would be nothing but links to the home pages > for various > other programming tools such as Strace and GDB. > > Granted, most programmers would already be aware of these tools, but > for folks coming from other platforms, it would be an quick and easy > source to the links for