Skip to content
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

Missing config file in 0.6.1 release #8

Closed
larandvit opened this issue Mar 24, 2019 · 6 comments
Closed

Missing config file in 0.6.1 release #8

larandvit opened this issue Mar 24, 2019 · 6 comments

Comments

@larandvit
Copy link

Hello,

I don't see "config" file to install it. I'm aware of issue #4.

The released tarball doesn't have "config" file. Also, when I try to run "./autogen.sh" file, it doesn't find other files.

./autogen.sh: line 3: autopoint: command not found
./autogen.sh: line 4: aclocal: command not found
./autogen.sh: line 5: automake: command not found
./autogen.sh: line 6: autoconf: command not found

Please advice.

Thank you.

@afrantzis
Copy link
Owner

Hi, it seems that your system is missing development tools. Which distribution and version are you using?

For Debian/Ubuntu, a quick way to get the required packages is: sudo apt build-dep bless

@larandvit
Copy link
Author

Thank you for response, @afrantzis.

I use CentOS 7 and bless package is not available when I run

sudo yum install bless

If I want to build it, what C# development tools do you use? Is it enough to install "dotnet-sdk-2.2". This is what I found for CentOS 7.

@larandvit
Copy link
Author

@afrantzis,
After installing dotnet-sdk-2.2 and prerequisites, I was able to build it for CentOS 7 64 bit with "./autogen.sh" file. It works fine.

"Step 4: Install the program" failed.

I separated a packaged to be deployed. Also, I installed those libraries as per https://www.centos.org/forums/viewtopic.php?t=58443

sudo yum install rarian-compat.x86_64 epel-release -y
sudo yum install mono-devel.x86_64 gtk-sharp2-devel.x86_64 -y

Thanks.

@afrantzis
Copy link
Owner

"Step 4: Install the program" failed.

Do you have output that could help figure out what went wrong?

@larandvit
Copy link
Author

Hi @afrantzis ,

The output of

sudo make install
Making install in po
make[1]: Entering directory `/home/developer/bless-0.6.1/po'
/usr/local/share
make[1]: execvp: /usr/local/share: Permission denied
make[1]: *** [install-data-yes] Error 127
make[1]: Leaving directory `/home/developer/bless-0.6.1/po'
make: *** [install-recursive] Error 1

It seems something with permissions and I ran a command

sudo ls -la /usr/local/share
total 0
drwxr-xr-x.  5 root root  49 Apr 11  2018 .
drwxr-xr-x. 12 root root 131 Apr 11  2018 ..
drwxr-xr-x.  2 root root  28 Mar 27 18:51 applications
drwxr-xr-x.  2 root root   6 Apr 11  2018 info
drwxr-xr-x. 21 root root 243 Apr 11  2018 man

Another command which was run before "sudo make install" for validation

make check
Making check in po
make[1]: Entering directory `/home/developer/bless-0.6.1/po'
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory `/home/developer/bless-0.6.1/po'
Making check in builder
make[1]: Entering directory `/home/developer/bless-0.6.1/builder'
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory `/home/developer/bless-0.6.1/builder'
Making check in src
make[1]: Entering directory `/home/developer/bless-0.6.1/src'
Making check in buffers
make[2]: Entering directory `/home/developer/bless-0.6.1/src/buffers'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/home/developer/bless-0.6.1/src/buffers'
Making check in gui
make[2]: Entering directory `/home/developer/bless-0.6.1/src/gui'
Making check in areas
make[3]: Entering directory `/home/developer/bless-0.6.1/src/gui/areas'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory `/home/developer/bless-0.6.1/src/gui/areas'
Making check in dialogs
make[3]: Entering directory `/home/developer/bless-0.6.1/src/gui/dialogs'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory `/home/developer/bless-0.6.1/src/gui/dialogs'
Making check in drawers
make[3]: Entering directory `/home/developer/bless-0.6.1/src/gui/drawers'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory `/home/developer/bless-0.6.1/src/gui/drawers'
Making check in plugins
make[3]: Entering directory `/home/developer/bless-0.6.1/src/gui/plugins'
make[3]: Nothing to be done for `check'.
make[3]: Leaving directory `/home/developer/bless-0.6.1/src/gui/plugins'
make[3]: Entering directory `/home/developer/bless-0.6.1/src/gui'
make[3]: Nothing to be done for `check-am'.
make[3]: Leaving directory `/home/developer/bless-0.6.1/src/gui'
make[2]: Leaving directory `/home/developer/bless-0.6.1/src/gui'
Making check in tools
make[2]: Entering directory `/home/developer/bless-0.6.1/src/tools'
make[3]: Entering directory `/home/developer/bless-0.6.1/src/tools'
make[3]: Nothing to be done for `check-am'.
make[3]: Leaving directory `/home/developer/bless-0.6.1/src/tools'
make[2]: Leaving directory `/home/developer/bless-0.6.1/src/tools'
Making check in util
make[2]: Entering directory `/home/developer/bless-0.6.1/src/util'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/home/developer/bless-0.6.1/src/util'
Making check in plugins
make[2]: Entering directory `/home/developer/bless-0.6.1/src/plugins'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/home/developer/bless-0.6.1/src/plugins'
make[2]: Entering directory `/home/developer/bless-0.6.1/src'
make[2]: Nothing to be done for `check-am'.
make[2]: Leaving directory `/home/developer/bless-0.6.1/src'
make[1]: Leaving directory `/home/developer/bless-0.6.1/src'
Making check in bin
make[1]: Entering directory `/home/developer/bless-0.6.1/bin'
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory `/home/developer/bless-0.6.1/bin'
Making check in data
make[1]: Entering directory `/home/developer/bless-0.6.1/data'
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory `/home/developer/bless-0.6.1/data'
Making check in doc
make[1]: Entering directory `/home/developer/bless-0.6.1/doc'
Making check in developer
make[2]: Entering directory `/home/developer/bless-0.6.1/doc/developer'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/home/developer/bless-0.6.1/doc/developer'
Making check in user
make[2]: Entering directory `/home/developer/bless-0.6.1/doc/user'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/home/developer/bless-0.6.1/doc/user'
make[2]: Entering directory `/home/developer/bless-0.6.1/doc'
make[2]: Nothing to be done for `check-am'.
make[2]: Leaving directory `/home/developer/bless-0.6.1/doc'
make[1]: Leaving directory `/home/developer/bless-0.6.1/doc'
Making check in .
make[1]: Entering directory `/home/developer/bless-0.6.1'
cd builder && make builder
make[2]: Entering directory `/home/developer/bless-0.6.1/builder'
make[2]: Nothing to be done for `builder'.
make[2]: Leaving directory `/home/developer/bless-0.6.1/builder'
/usr/bin/mono builder/bless-builder.exe BlessTests -nowarn:0169  -d:ENABLE_UNIX_SPECIFIC
>> Building module BlessTests.Buffers...
Package nunit was not found in the pkg-config search path.
Perhaps you should add the directory containing `nunit.pc'
to the PKG_CONFIG_PATH environment variable
No package 'nunit' found
error CS8027: Error running pkg-config. Check the above output.
Failed
make[1]: *** [check-am] Error 1
make[1]: Leaving directory `/home/developer/bless-0.6.1'
make: *** [check-recursive] Error 1

@afrantzis
Copy link
Owner

I have pushed a fix for make install to master. To use make check you need to install the nunit-console command (if it is available on your distro).

Also note that you can run bless from within the source directory after make, system installation is not required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants