Raman normally requests patches go to the list. Note that I'm not sure how much you need to worry about the warnings. These are just that, warnings and should not affect creation/compilation of the info files. I didn't actually see any 'errors' in the list, but only ran over it quickly, so must have missed them. The warnings I did see looked harmless and were just alerts regarding possible inconsistencies - just like the warnings in compiling emacs - best avoided if possible, but not critical. Tim Steve Holmes writes: > Well at this point, it isn't unique to Arch Linux since I got it to > build. The rest of the package appears fine. It's just the errors in > the TexInfo stuff so I will begin playing with that till I can get rid > of the errors and warnings. That should get the package to build > completely without hacking the Makefile or any of that. I'm still > green enough with emacspeak to see some value in the info pages. > > When I get some fixes done, are patches allowed to go to the list or > is there a different way to submit fixes? > > On 3/20/13, Tim Cross <email@example.com> wrote: > > Steve Holmes writes: > > > Still looking for how to fix the info target to build correctly > > > though. I could mess around with the texinfo pages and see if I can > > > correct the errors myself and provide a patch or something but I know > > > little about texinfo let alone track down someone else's text bugs. > > > > > > > Sounds like an excellent learning opportunity for you there Steve :-) > > > > Seriously though, from your explination, I suspect the problem is quite > > trivial > > and won't be difficult to locate. I don't think we have many arch linux > > users, > > so your contribution to fixing this, in addition to being very appreciated, > > may > > be the only fix we get. Therefore, I hope and encourage you to give it a try > > - > > at the very least, it will mean you avoid the same hack next time you have > > to > > update. > > > > I personally don't bother doing make install. I run emacspeak from the > > build > > directory and just add the info files to my info path. To be hones, it has > > been > > years since I've even looked at the info files for emacspeak. > > > > Tim > > > > > > > > -- > > Tim Cross > > IT Security Manager > > Information Technology > > University of New England > > Phone: +61 2 6773 3210 > > Mobile: 0428 212217 > > E-Mail: firstname.lastname@example.org > > Web: http://www.une.edu.au/itd > > --- > > Please avoid sending me Word or PowerPoint attachments. > > See http://www.gnu.org/philosophy/no-word-attachments.html > > > > Any fool can make things bigger, more complex, and more violent. It takes a > > touch of genius (and a lot of courage) to move in the opposite direction. > > âAlbert Einstein > > > > > > > > > > > > > > -- Tim Cross IT Security Manager Information Technology University of New England Phone: +61 2 6773 3210 Mobile: 0428 212217 E-Mail: email@example.com Web: http://www.une.edu.au/itd --- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html Any fool can make things bigger, more complex, and more violent. It takes a touch of genius (and a lot of courage) to move in the opposite direction. âAlbert Einstein ----------------------------------------------------------------------------- To unsubscribe from the emacspeak list or change your address on the emacspeak list send mail to "firstname.lastname@example.org" with a subject of "unsubscribe" or "help".
If you have questions about this archive or had problems using it, please send mail to:email@example.com No Soliciting!
Emacspeak List Archive | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | 1998 | Pre 1998
Emacspeak Files | Emacspeak Blog | Search the archive