public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Laura Eaves" <leaves1@carolina.rr.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Could someone compile flite for me?
Date: Mon, 5 Sep 2005 16:12:50 -0400	[thread overview]
Message-ID: <061701c5b256$30d404e0$7401a8c0@Charmin> (raw)
In-Reply-To: <8e65427144c543c6bdf2332c17b42442@digitaldarragh.com>

You really don't want to run 2 versions of a compiler.
There are some little gotchas if you happen to link a library compiled with 
one to an executable of another.  In some rare cases you may get different 
or wrong behavior.
But that being said, you can install and use as many compilers as you want 
on a system -- just rename the command so they will be differentiable, and 
be sure to put the compilation system files -- libraries, includes, 
supporting commands -- in separate directories.
--le
Good luck.

----- Original Message ----- 
From: "Darragh" <lists@digitaldarragh.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, September 05, 2005 3:12 PM
Subject: Could someone compile flite for me?


Hello all,
I have the sources of FLITE here but they won't compile.  I think its 
because I have a version of GCC that has too many differences than the one 
used by the developer of FLITE.

If someone could compile it for me and send me the result I'd really 
appreciate it. Email me off list at d@digitaldarragh.com and I'll send you 
the source.  I've got the latest version from their website.

Oh finally, does anyone know of a way of running two versions of a compiler 
on the one machine concurrently?


Thanks in advance


Darragh

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup 



  reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Darragh
 ` Laura Eaves [this message]
 ` Janina Sajka
 Darragh
 ` Janina Sajka

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='061701c5b256$30d404e0$7401a8c0@Charmin' \
    --to=leaves1@carolina.rr.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).