public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: help with compilation?
Date: Sat, 7 Jan 2006 11:29:21 -0800	[thread overview]
Message-ID: <000801c613c0$a9191640$2cc69245@dataplus4puarg> (raw)
In-Reply-To: <000101c61347$c0e64500$230110ac@main>

Hay,
I fixed it. I just left the port, and set it in the command line.
I would like to know how to edit still, but the server is up!
Thanks,
Tyler Littlefield.
Check out our website:
http://tysplace.the-leetest.net
check out my blog:
livejournal.com/~tylerrl
[my programs don't have bugs, just randomly added features]
[failure is not an option, it comes bundled with windows!]
----- Original Message ----- 
From: "Jim Grimsby" <jimgrims@pacbell.net>
To: "'Speakup is a screen review system for Linux.'" 
<speakup@braille.uwo.ca>
Sent: Friday, January 06, 2006 9:03 PM
Subject: RE: help with compilation?


> Hi the below message is useless.  When you get errors you got to report
> what the errors are.  Some thing about what ever tells us nothing.  If
> you are using speakup block the error copy it and put it in a text file
> so we can see what the error is.
> Hth
>
> jim grimsby
> msn: jim.grimsby@att.net
> email:  jimgrims@pacbell.net
> skype: jim.grimsby
>
> -----Original Message-----
> From: speakup-bounces@braille.uwo.ca
> [mailto:speakup-bounces@braille.uwo.ca] On Behalf Of tyler
> Sent: Friday, January 06, 2006 7:19 PM
> To: Speakup is a screen review system for Linux.
> Subject: help with compilation?
>
>
> Hay,
> I am compiling a server via ssh. I do the configure, and everything
> works
> fine. Then, I fill out the options.h file like a good kid, and
> everything
> should still be going fine... Wait, anyone notice the keyword back
> there?
> use your up arrow, and check for it. lol. Anyway, When I compile, I get
> a
> bunch of errors. Actually, someone might be farmilliar with it. It is
> the
> moo server. Now, this is uploading the server untared and uncompressed
> to
> the linux system. When I downloaded the folder, and did tar -xzvf, it
> gave
> me an error, and said something about the headers, so it couldn't finish
>
> extracting the file.
> Lost there to.
> A fix to either one of these problems would be awesome.
> Thanks,
> Tyler Littlefield.
> Check out our website:
> http://tysplace.the-leetest.net
> check out my blog:
> livejournal.com/~tylerrl
> [my programs don't have bugs, just randomly added features] [failure is
> not an option, it comes bundled with windows!]
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 



  parent reply	other threads:[~ UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 tyler
 ` Jim Grimsby
   ` tyler
     ` Gregory Nowak
       ` tyler
       ` Sina Bahram
         ` tyler
           ` Sina Bahram
       ` Butch Bussen
         ` tyler
   ` tyler [this message]
 ` Lorenzo Taylor
   ` tyler
     ` tyler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000801c613c0$a9191640$2cc69245@dataplus4puarg' \
    --to=compgeek13@gmail.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).