Page 1 of 1

./Config Error with TRE

Posted: Sun Aug 08, 2010 12:19 am
by nameless
Hi guys. I'm trying to install Unreal 3.2.8 on Debian 5 (lenny) and I'm getting the following error when I do ./Config

Code: Select all

extracting TRE regex library
cp: cannot stat `tre.tar.gz': No such file or directory
gzip: tre.tar.gz: No such file or directory
cp: cannot stat `tre.tar.gz.bak': No such file or directory
tar: tre.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
configuring TRE regex library
./configure: line 12976: cd: tre-0.7.5: No such file or directory
./configure: line 12977: ./configure: No such file or directory
I'm a bit confused because when I run

Code: Select all

whereis tre
I get

Code: Select all

tre: /usr/include/tre
So as far as I can tell, I've got tre installed and unreal doesn't know where to look for it.

I'm still new on the sysadmining stuff, so maybe I'm missing something really obvious. Any help would be appreciated.

Re: ./Config Error with TRE

Posted: Sun Aug 08, 2010 2:47 am
by katsklaw
delete your tarball and install directory, if you have edited your config, save it. redownload the tarball from the official source and try again. tre ships with Unreal and it missing suggests corrupted/incomplete download.

Re: ./Config Error with TRE

Posted: Sun Aug 08, 2010 4:18 am
by nameless
Redownloaded the tar file and then checked it via md5, sha1, and gpg. The values checked out, but I'm still having the same problem

Re: ./Config Error with TRE

Posted: Sun Aug 08, 2010 7:13 am
by Stealth
Unreal does not use the system TRE. Instead it uses the TRE packaged in the Unreal tarball. This is mostly because Unreal is very version-specific about the functions offered by TRE and how to call them.

What you need to do is make sure the TRE tarball is present and readable by the Config script. The TRE tarball is located in the extras directory of the Unreal tarball.

I do believe Unreal 3.2.9 will use the system TRE if present.

Re: ./Config Error with TRE

Posted: Sun Aug 08, 2010 7:00 pm
by nameless
Hrm, I ran ./Config as root and it ran just fine. Seems to be something I mis-configured in Debian. Thanks for the help