New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install failure - texy src location not found #253
Comments
Try now. Texy PEAR channel was down. |
Great! install went well, but now it can't load the texy lib
Current error:
If i do a locate over my system, i can find texy here: /usr/share/php/texy/src/Texy/Texy.php |
I fixed by manually changing the /usr/bin/apigen file. This is a diff:
|
I will try to prepare ApiGen 2.8.1 this week a resolve this. There's probably new directory structure in new Texy version. And PEAR is stupid and doesn't follow dependecies. |
I just made the pull request for it: #254 Please review |
@kukulich great thanks! |
@marosoft it's work! |
@kukulich any update on when this issue will be fixed? thanks! |
Which version combinations do I have to install to get this to work atm? |
@kukulich What version is working right now? |
I just created a symbolic link on my system (Mint 15) as a workaround
|
This still seems to be an issue. I installed from pear now and apigen died with
|
Still seeing it myself |
Confirmed still a bug - installed yesterday, script still looking in /usr/share/php/Texy/texy.php changing to /usr/share/php/texy/src/texy.php about line 30 of the apigen script in /usr/bin fixes problem |
I just installed Apigen and am seeing the same issue:
|
Issue storyI just installed ApiGen and got the same issue here:
Facts
|
the same issue here:
|
ping @kukulich |
Still broken, same message as above, on PHP 5.4.6-1ubuntu1.4, installed through PEAR. #253 (comment) fixes the problem if anyone needs a workaround |
on mac 10.8 |
quick fix on windows: |
this happens to me using 3.0 version installed via composer, 2.8 does not produce this error if you want to use 3.0 and avoid this persisting bug you can add texy to php's include_path directive |
Installed ApiGen 2.8.0 through PEAR and receiving the following errors:
|
@marosoft, your solutions is work for me. Thanks alot. |
Just ran into this. Solution provided by @lloc worked. |
Installed via pear on WAMP on Windows 7 I had to edit the paths on line 30 and line 42 in apigen file after this it worked. |
Solution provided by @lloc is perfect!, thanks. |
@robinfai on mac osx 10.9 this does not work..anything else suggested for osx mavericks guys? |
I've had success using the standalone packages if you've got no other options: https://github.com/apigen/apigen/downloads |
Will be fixed in version 2.9.0. |
@marosoft, your solutions is work for me. Thanks alot. |
Editting the apigen script is what worked for me on Snow Leopard. PEAR installed set_include_path('/usr/local/Cellar/php53/5.3.26/lib/php/');
@include '/usr/local/Cellar/php53/5.3.26/lib/php/Nette/loader.php';
@include '/usr/local/Cellar/php53/5.3.26/lib/php/texy/src/texy.php'; Comment out the other two line in the block. |
I use Fedora 20 x64 and PHP 5.5 and I had the same problems today to installing Apigen.. // This default path not exists in my OS, so I commented it.
//include '/usr/share/pear/Texy/texy.php';
// This path exists in my OS, so I added it.
include '/usr/share/pear/texy/src/texy.php'; I see this issue has not been resolved yet on Pear repo, I hope you can solve this. |
Same problem here with 2.8.0 (I don't see a 2.8.1 release yet); @robinfai's workaround (creating Text.php as a symbolic link) worked for me. |
This project hasn't been updated in a while.. I'm not confident that this issue will be resolved. Too bad. |
@marosoft fix worked for me. |
Just installed v2.8.0 and I have the same problem. (Ubuntu 12.04) |
Thanks mamdouhweb! It worked for me too. |
I'm experienced the same issue on Ubuntu 14.04. I just installed both pear and apigen, so it's a really fresh install. @quincyglenn workaround worked for me. |
When i try to install apigen with pear, i get this error:
Anyone with the same issue?
The text was updated successfully, but these errors were encountered: