* upgrading BRLTTY @ Daniel Dalton ` Willem van der Walt ` Geoff Shang 0 siblings, 2 replies; 9+ messages in thread From: Daniel Dalton @ UTC (permalink / raw) To: Linux for blind general discussion Hi, I will post here as well since I didn't get an answer on the brltty mailing list. Sorry if you get this twice. I got the brltty tar ball. When running make I get an error all two. Any ideas what's wrong? Also does anyone know why it says unknown version when I type ./configure? Or something about revision. What compilers and stuff do I need. I unpacked it of course... Daniel ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: upgrading BRLTTY upgrading BRLTTY Daniel Dalton @ ` Willem van der Walt ` Daniel Dalton ` Geoff Shang 1 sibling, 1 reply; 9+ messages in thread From: Willem van der Walt @ UTC (permalink / raw) To: Linux for blind general discussion First do apt-get update and then apt-get install brltty and see if you do not get a version new enough. You must give more information regarding your make error, on what you gave below, no one will be able to help you. On Wed, 21 Nov 2007, Daniel Dalton wrote: > Hi, > I will post here as well since I didn't get an answer on the brltty mailing > list. Sorry if you get this twice. > > > I got the brltty tar ball. When running make I get an error all two. Any ideas > what's wrong? Also does anyone know why it says unknown version when I type > ./configure? Or something about revision. What compilers and stuff do I need. > I unpacked it of course... > Daniel > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: upgrading BRLTTY ` Willem van der Walt @ ` Daniel Dalton ` Willem van der Walt 0 siblings, 1 reply; 9+ messages in thread From: Daniel Dalton @ UTC (permalink / raw) To: Linux for blind general discussion On 21/11/2007 6:18 PM, Willem van der Walt wrote: > First do > apt-get update > and then apt-get install brltty > and see if you do not get a version new enough. That didn't work. > You must give more information regarding your make error, on what you gave > below, no one will be able to help you. Sure. Do you know how to scroll the terminal so I can see the previous screen which has some of the configure output on it? (With brltty or speakup) Thanks. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: upgrading BRLTTY ` Daniel Dalton @ ` Willem van der Walt ` Daniel Dalton 0 siblings, 1 reply; 9+ messages in thread From: Willem van der Walt @ UTC (permalink / raw) To: Linux for blind general discussion Once ./configure failled, do: ls *log to see if you have a configure.log or sutch. If you do, use less configure.log to read it. You can also do: script output.lo then do ./configure then do: exit the output will be in output.log. g On Wed, 21 Nov 2007, Daniel Dalton wrote: > On 21/11/2007 6:18 PM, Willem van der Walt wrote: > > First do > > apt-get update > > and then apt-get install brltty > > and see if you do not get a version new enough. > > That didn't work. > > > You must give more information regarding your make error, on what you gave > > below, no one will be able to help you. > > Sure. Do you know how to scroll the terminal so I can see the previous screen > which has some of the configure output on it? > (With brltty or speakup) > Thanks. > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: upgrading BRLTTY ` Willem van der Walt @ ` Daniel Dalton ` Willem van der Walt 0 siblings, 1 reply; 9+ messages in thread From: Daniel Dalton @ UTC (permalink / raw) To: Linux for blind general discussion It seems that if I type ./configure > file.txt I get all the warnings on screen... So how do I scroll up the terminal? I want to know this for other things too... Thx. On 21/11/2007 8:39 PM, Willem van der Walt wrote: > Once ./configure failled, do: > ls *log > to see if you have a configure.log or sutch. > If you do, use less configure.log to read it. > You can also do: > script output.lo > then do ./configure > then do: > exit > the output will be in output.log. > g > > On Wed, 21 Nov 2007, Daniel Dalton wrote: > >> On 21/11/2007 6:18 PM, Willem van der Walt wrote: >>> First do >>> apt-get update >>> and then apt-get install brltty >>> and see if you do not get a version new enough. >> That didn't work. >> >>> You must give more information regarding your make error, on what you gave >>> below, no one will be able to help you. >> Sure. Do you know how to scroll the terminal so I can see the previous screen >> which has some of the configure output on it? >> (With brltty or speakup) >> Thanks. >> >> _______________________________________________ >> Blinux-list mailing list >> Blinux-list@redhat.com >> https://www.redhat.com/mailman/listinfo/blinux-list >> >> > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: upgrading BRLTTY ` Daniel Dalton @ ` Willem van der Walt ` Samuel Thibault 0 siblings, 1 reply; 9+ messages in thread From: Willem van der Walt @ UTC (permalink / raw) To: Linux for blind general discussion On Thu, 22 Nov 2007, Daniel Dalton wrote: > It seems that if I type ./configure > file.txt > I get all the warnings on screen... If you want to do it with redirection, you need to redirect both stdin and stderr to the file. ./configure 2>1 > file.txt > > So how do I scroll up the terminal? > I want to know this for other things too... > Thx. In text mode which is what you are using, you cannot scroll up the screen. In some cases, you can pipe the output into less, acommand which displays the content screen by screen with the ability to go up a screen by hitting the b key. > > On 21/11/2007 8:39 PM, Willem van der Walt wrote: > > Once ./configure failled, do: > > ls *log > > to see if you have a configure.log or sutch. > > If you do, use less configure.log to read it. > > You can also do: > > script output.lo > > then do ./configure > > then do: > > exit > > the output will be in output.log. > > g > > > > On Wed, 21 Nov 2007, Daniel Dalton wrote: > > > > > On 21/11/2007 6:18 PM, Willem van der Walt wrote: > > > > First do > > > > apt-get update > > > > and then apt-get install brltty > > > > and see if you do not get a version new enough. > > > That didn't work. > > > > > > > You must give more information regarding your make error, on what you > > > > gave > > > > below, no one will be able to help you. > > > Sure. Do you know how to scroll the terminal so I can see the previous > > > screen > > > which has some of the configure output on it? > > > (With brltty or speakup) > > > Thanks. > > > > >> _______________________________________________ > > > Blinux-list mailing list > > > Blinux-list@redhat.com > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: upgrading BRLTTY ` Willem van der Walt @ ` Samuel Thibault ` coscell 0 siblings, 1 reply; 9+ messages in thread From: Samuel Thibault @ UTC (permalink / raw) To: Linux for blind general discussion Willem van der Walt, le Thu 22 Nov 2007 10:55:51 +0200, a écrit : > > > On Thu, 22 Nov 2007, Daniel Dalton wrote: > > > It seems that if I type ./configure > file.txt > > I get all the warnings on screen... > If you want to do it with redirection, you need to redirect both stdin and > stderr to the file. > ./configure 2>1 > file.txt It should rather be ./configure > file.txt 2>&1 Because else 2>&1 makes stderr to stdout before stdout got redirected to the file. Samuel ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: upgrading BRLTTY ` Samuel Thibault @ ` coscell 0 siblings, 0 replies; 9+ messages in thread From: coscell @ UTC (permalink / raw) To: Linux for blind general discussion ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: upgrading BRLTTY upgrading BRLTTY Daniel Dalton ` Willem van der Walt @ ` Geoff Shang 1 sibling, 0 replies; 9+ messages in thread From: Geoff Shang @ UTC (permalink / raw) To: Linux for blind general discussion Hi, Some general advice about compiling. First, read the ReadMe file and, if there is one, the Install file that comes with the source code you're trying to compile. These should tell you about any dependencies you might need. NOte that if you're using a package-based distribution such as redhat/fedora or Debian/Ubuntu, you will need the development versions of any required libraries, not just the runtime versions. For Redhat and Fedora, this will usually involve installing a package with devel in the name, for Debian and Ubuntu the package will have dev in the name. Second, if ./configure fails, don't bother trying to run Make. Configure will usually only indicate an error if something important is missing. Unless configure is able to complete successfully, the sources won't be ready for you to run make. finally, if you do get to running make and it errors out, the important information will not be the final line of output, but several lines further up. The error will usually indicate a particular type of error in a specific line of a file. Hope this helps. My advice is, unless you really need to upgrade anything, you might want to stick with using packages for now, as compiling can get complicated if things aren't quite right with the code you're compiling. and if you do need to upgrade, you may be able to install a more recent package, rather than having to compile it from sources. Geoff. ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
upgrading BRLTTY Daniel Dalton
` Willem van der Walt
` Daniel Dalton
` Willem van der Walt
` Daniel Dalton
` Willem van der Walt
` Samuel Thibault
` coscell
` Geoff Shang
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).