On Fri, 17 Jun 2011, Greg' Ar Tourter wrote:
I wouldn't worry too much about xulrunner.
Greg,
Then I won't, either. Stopped the download and removed the directory.
as for the name change, adobe renamed it adobe-reader so it was decided to
follow upstream in the naming convention. I should
Hi Rich,
I wouldn't worry too much about xulrunner. It is a dependency that was
noted when I inherited the maintenance. it works without it (it is
just that you can see an error if you call acroread from the command
line which disappears when xulrunner is installed. I still haven't
figured out wha
On Fri, 17 Jun 2011, Greg' Ar Tourter wrote:
For acroread (which I maintain) you need to run the
/usr/bin/update-pango-querymodules script so that the module file is
created for 32bit as well as 64bit. It should do this automatically at
the next reboot but running it manually should get you goin
For acroread (which I maintain) you need to run the
/usr/bin/update-pango-querymodules script so that the module file is
created for 32bit as well as 64bit. It should do this automatically at
the next reboot but running it manually should get you going.
Hope this helps
Cheers
Greg
On 17 June 20
On Fri, 17 Jun 2011, Rich Shepard wrote:
The three applications that won't build or run properly are graphviz (low
priority as I've not used it before), acroread (builds but does not
properly display menu fonts), and epdfview (which won't build). The latter
two are rather critical and I need to
On Fri, 17 Jun 2011, Audrius Ka?ukauskas wrote:
Have you tried what Greg suggested? He was successful at compiling
graphviz on a multilib system.
Breaking news: graphviz just built when I changed LD_LIBRARY_PATH for both
user me and root to lib64 rather than lib. Hoo-ha!
Now I need the s
On Fri, 17 Jun 2011, Audrius Ka?ukauskas wrote:
Have you tried what Greg suggested? He was successful at compiling
graphviz on a multilib system.
Yes, I have. /etc/profile.d/32dev.sh is not executable. All references to
'lib' are now 'lib64' in the package and library paths.
The three ap
On Fri, 2011-06-17 at 06:38:11 -0700, Rich Shepard wrote:
> On Thu, 16 Jun 2011, B Watson wrote:
>
> >Well, no, I was saying to make sure /usr/lib/pkgconfig is *not* listed in
> >your PKG_CONFIG_PATH (and make sure /usr/lib64/pkgconfig *is* in there).
>
> Darn! I changed PKG_CONFIG_PATH in both
On Thu, 16 Jun 2011, B Watson wrote:
Well, no, I was saying to make sure /usr/lib/pkgconfig is *not* listed in
your PKG_CONFIG_PATH (and make sure /usr/lib64/pkgconfig *is* in there).
Darn! I changed PKG_CONFIG_PATH in both ~/.bash_profile and
/root/.bash_profile, sourced the latter, and sti
On 6/16/11, Rich Shepard wrote:
>> Another thing to check is PKG_CONFIG_PATH in the environment. It shouldn't
>> include /usr/lib/pkgconfig (if it's not set, set it to something like
>> /usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig:/usr/local/lib64/pkgconfig
>> in your .bash_profile or whatever
On Thu, 16 Jun 2011, Slacker build user wrote:
On the other hand, I have used Graphviz quite a bit for several years and
do in fact find it very useful. I would encourage you to grit your teeth
and get it running - it is worth some effort, and then you will know what
you might have missed!
Rob
Rich Shepard wrote:
Well, since I've not had success building graphviz on earlier releases
either I don't know that I really need it. It looks potentially useful, but
I have no experience with it. It can wait and I won't miss what I don't
know. :-)
I wish I could help - but no 64 bit access a
Hi,
I have just compiled graphviz on a multilib system without any issues
and without modifying anything.
The only thing I can think off is that you have run the
/etc/profile.d/32dev.sh before trying to compile it which you
shouldn't if you are trying to compile a 64bit package. Make should
the s
On Thu, 16 Jun 2011, B Watson wrote:
Nope. The build scripts are tested & supported only on non-multilib (pure
64-bit). This gets mentioned pretty often on this mailing list...
Sigh. Since I only very recently installed 64-bit Slackware-13.37 on my
Dell Latitude I've not paid attention to 64
On 6/16/11, Rich Shepard wrote:
>Graphviz tells me it cannot find a library which is in /usr/lib64; it's
> looking in /usr/lib. Is this a build script error?
Nope. The build scripts are tested & supported only on non-multilib
(pure 64-bit). This gets mentioned pretty often on this mailing li
If I have missed something with the installation of the multilib and
compat32 libraries, how should I re-do the process to fix the errors?
Graphviz tells me it cannot find a library which is in /usr/lib64; it's
looking in /usr/lib. Is this a build script error?
libtool: link: warning: /usr/l
16 matches
Mail list logo
