John J. Boyer wrote:
Les,
I installed the development tools and development libraries, as you
suggested. I even tried to install packages x*.x86_64 There were some
unresolved dependencies in the latter, so I used --skip-broken with yum.
There was a report of conflicting files, so i don't
Ljubomir Ljubojevic wrote:
John J. Boyer wrote:
Les,
I installed the development tools and development libraries, as you
suggested. I even tried to install packages x*.x86_64 There were some
unresolved dependencies in the latter, so I used --skip-broken with yum.
There was a report of
On 5/17/2011 12:49 AM, John J. Boyer wrote:
Les,
I installed the development tools and development libraries, as you
suggested. I even tried to install packages x*.x86_64 There were some
unresolved dependencies in the latter, so I used --skip-broken with yum.
There was a report of
Les,
Here's my autogen.sh file.
#!/bin/sh
#
# autogen.sh glue for liblouis
#
# Requires: automake 1.9, autoconf 2.57+
# Conflicts: autoconf 2.13
set -e
# Refresh GNU autotools toolchain.
echo Cleaning autotools files...
find -type d -name autom4te.cache -print0 | xargs -0 rm -rf \;
find -type f
The repository to which I am referring is the liblouis repository on
googlecode. I get a working copy, which has an autogen.sh file. I run
this and then configure. Make gives the following errors
../libtool: line 826: X--tag=CC: command not found
../libtool: line 859: libtool: ignoring unknown
I haven't had this many errors doing a make in a long, long, long, long
time... maybe never. (I'm saying that I'm guessing here) It could
be that you were in the wrong directory when you ran make or, more
likely, you skipped a command (perhaps .configure) that should have
been run before
Hello John,
On Mon, 2011-05-16 at 01:43 -0500, John J. Boyer wrote:
../libtool: line 1136: X-I.: command not found
../libtool: line 1136: X-I../../gnulib: No such file or directory
../libtool: line 1136: X-I../liblouis: No such file or directory
../libtool: line 1136: X-g: command not found
On Mon, May 16, 2011 at 12:32 AM, John J. Boyer
john.bo...@abilitiessoft.com wrote:
I have a CentOS virtual private server from 1and1.com If I checkout or
pull something from a repository, it will contain an autogen.sh file
Running this and then configure seems to work. However, when I run make
I have a CentOS virtual private server from 1and1.com
This may be a non-issue but have you tried compiling stuff before on
this machine? Most of the VPS system's I've seen in operation have
stripped out the build tools for performance security reasons.
--
Drew
Nothing in life is to be
On 5/16/2011 1:05 PM, Drew wrote:
I have a CentOS virtual private server from 1and1.com
This may be a non-issue but have you tried compiling stuff before on
this machine? Most of the VPS system's I've seen in operation have
stripped out the build tools for performance security reasons.
If
Les,
I installed the development tools and development libraries, as you
suggested. I even tried to install packages x*.x86_64 There were some
unresolved dependencies in the latter, so I used --skip-broken with yum.
There was a report of conflicting files, so i don't know how much was
I have a CentOS virtual private server from 1and1.com If I checkout or
pull something from a repository, it will contain an autogen.sh file
Running this and then configure seems to work. However, when I run make
I get a lot of error messages from libtool saying that such and such a
command
On 05/15/2011 11:32 PM, John J. Boyer wrote:
I have a CentOS virtual private server from 1and1.com If I checkout or
pull something from a repository, it will contain an autogen.sh file
Running this and then configure seems to work. However, when I run make
I get a lot of error messages from
On Sun, May 15, 2011 at 11:32:24PM -0500, John J. Boyer wrote:
I have a CentOS virtual private server from 1and1.com If I checkout or
pull something from a repository, it will contain an autogen.sh file
Running this and then configure seems to work. However, when I run make
I get a lot of
14 matches
Mail list logo
