[gentoo-user] Pixie does not run.

[gentoo-user] Pixie does not run.

[Adrian]

Greetings;

When I try to run pixie I get the following result:

Wed Aug 31 06:23:19
~
 skippi $  pixie
pixie: symbol lookup error: /usr/lib/libdpstk.so.0: undefined symbol:
DPSDefaultErrorProc

I tried to re-emerge pixie in order to see if that gave me any useful
error messages.  It emerged quite happily, no problem.

I did a linux google search for this error message and found nothing at
all, which strikes me as odd . . .
Also checked the bug reports for anything on pixie and found nothing.

I guessing (and guessing I am) the problem isn't with pixie, but with
one of the libraries it needs.  Is the thing to do find out which
package libdpstk.so.0 is a part of and try to re-emerge that package?

Any suggestions?  Much thanks.
Adrian


-- 
On The Fly Photography -:- Creation From Chaos

On The Fly Photography:  http://204EastSouth.com
Purchase from On The Fly:  http://204EastSouth.com/OTFStore.htm
-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] Pixie does not run.

[Dave Nebinger]

> pixie: symbol lookup error: /usr/lib/libdpstk.so.0: undefined symbol:
> DPSDefaultErrorProc

A google search for libdpstk indicates that this is a core library for x11
with some references to it being obsolete.  I've got one for my xorg-x11
install, so it must not be too obsolete...

A google search for DPSDefaultErrorProc brought back a pointer to the header
file xc/include/DPS/dpsclient.h which seems to indicate that
DPSDefaultErrorProc is the default error handler for postscript error
reporting.  Being that it's the default, it definitely should be in the
libs...

Using the nm tool with find, I see that the DPSDefaultErrorProc is marked as
undefined in libdpstk.so, but appears to be defined in libdps.so.

So it would appear that you have some sort of linking issue going on...

For a quick fix I'd suggest trying to build pixie manually and ensure that
you include a -ldps in your LDFLAGS.

Whether it's a bug or not in the ebuild I couldn't venture to guess.



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Pixie does not run.

[Adrian]

On Wed, 31 Aug 2005 09:15:33 -0400
"Dave Nebinger" <dnebinger@joat.com> wrote the words:

> > pixie: symbol lookup error: /usr/lib/libdpstk.so.0: undefined
> > symbol: DPSDefaultErrorProc
> 
> A google search for libdpstk indicates that this is a core library for
> x11 with some references to it being obsolete.  I've got one for my
> xorg-x11 install, so it must not be too obsolete...
> 
> A google search for DPSDefaultErrorProc brought back a pointer to the
> header file xc/include/DPS/dpsclient.h which seems to indicate that
> DPSDefaultErrorProc is the default error handler for postscript error
> reporting.  Being that it's the default, it definitely should be in
> the libs...
> 
> Using the nm tool with find, I see that the DPSDefaultErrorProc is
> marked as undefined in libdpstk.so, but appears to be defined in
> libdps.so.
> 
> So it would appear that you have some sort of linking issue going
> on...
> 
> For a quick fix I'd suggest trying to build pixie manually and ensure
> that you include a -ldps in your LDFLAGS.
> 
> Whether it's a bug or not in the ebuild I couldn't venture to guess.

Hi Dave --  thanks for the response.  I'm not sure I understand it all,
but I understand enough to get me started and do some testing.  One
question however, when you say to build pixie manually, what do you mean
by building it manually?  Is that different from 

emerge pixie

??

If you could clarify for me I would be most grateful.  Thanks much.
Adrian



-- 
On The Fly Photography -:- Creation From Chaos

On The Fly Photography:  http://204EastSouth.com
Purchase from On The Fly:  http://204EastSouth.com/OTFStore.htm
The Cynical Libertarian Society:  http://www.204EastSouth.com/cls
-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] Pixie does not run.

[Dave Nebinger]

> Hi Dave --  thanks for the response.  I'm not sure I understand it all,
> but I understand enough to get me started and do some testing.  One
> question however, when you say to build pixie manually, what do you mean
> by building it manually?  Is that different from
> 
> emerge pixie

Yeah.  Basically you do the following:

1. get the tarball either from the home site or /usr/portage/distfiles to
your home directory.  Usually if I'm going to do a manual build I grab the
latest stable distribution from the home site.
2. extract the tarball then cd into the directory.
3. Run the configure script, but you have two options: a) use "./configure
--prefix=/usr" to replace the pixie that portage emerged or b) use
"./configure --prefix=/usr/local" to get a clean local copy.
4. Build using the make command.
5. At this point you can test in the local directory to see if it works.
6. If you're happy with the build, su then "make install".



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Pixie does not run.

[Adrian]

On Thu, 01 Sep 2005 08:51:23 -0400
"Dave Nebinger" <dnebinger@joat.com> wrote the words:

> > Hi Dave --  thanks for the response.  I'm not sure I understand it
> > all, but I understand enough to get me started and do some testing. 
> > One question however, when you say to build pixie manually, what do
> > you mean by building it manually?  Is that different from
> > 
> > emerge pixie
> 
> Yeah.  Basically you do the following:
> 
> 1. get the tarball either from the home site or /usr/portage/distfiles
> to your home directory.  Usually if I'm going to do a manual build I
> grab the latest stable distribution from the home site.
> 2. extract the tarball then cd into the directory.
> 3. Run the configure script, but you have two options: a) use
> "./configure --prefix=/usr" to replace the pixie that portage emerged
> or b) use "./configure --prefix=/usr/local" to get a clean local copy.
> 4. Build using the make command.
> 5. At this point you can test in the local directory to see if it
> works. 6. If you're happy with the build, su then "make install".


Oh, duh...  I have done an
./configure
make
make install
since I started using Gentoo.  How soon we forget.  Actually it was just
a terminology problem of me not grasping what you said.  If I replace
the pixie emerged by portage does that mess up anything as far as
portage is concerned?  

I expect there is something out there about my question.  I'll have to
go looking when I have time.  I'll probably try your suggestions this
weekend.  Much too busy at the moment to play with this right now.  

I have one more dumb question.  What man page do I read to understand
how to use LDFLAGS?  I was thinking this was a variable in make.conf
however I just read the man page for make.conf and I see that it is not
documented there.  Also looked around at gentoo.org documentation, but
didn't find anything that helps yet.

Again, thank you very much for your time and assistance.

Adrian



-- 
On The Fly Photography -:- Creation From Chaos

On The Fly Photography:  http://204EastSouth.com
Purchase from On The Fly:  http://204EastSouth.com/OTFStore.htm
The Cynical Libertarian Society:  http://www.204EastSouth.com/cls
-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] Pixie does not run.

[Dave Nebinger]

> If I replace
> the pixie emerged by portage does that mess up anything as far as
> portage is concerned?

Well, other than if an upgrade comes through emerge --update world would try
to overwrite what you install.

Otherwise portage will think it's in there.

> I have one more dumb question.  What man page do I read to understand
> how to use LDFLAGS?  I was thinking this was a variable in make.conf
> however I just read the man page for make.conf and I see that it is not
> documented there.  Also looked around at gentoo.org documentation, but
> didn't find anything that helps yet.

LDFLAGS typically come in the -llib and -Lpath variety and are used to
ensure that additional libraries and paths are included in the link phase.
You typically won't need to add these (which is probably why there is little
if any reference in the gentoo doc).

Obviously there are more uses for LDFLAGS, but those above are used the
most.

If you do need them you can set up your environment variables before doing
the make process.  You can also use them on the command line ala
"LDFLAGS=-llib make", etc.



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Pixie does not run.

[Adrian]

On Fri, 02 Sep 2005 10:29:30 -0400
"Dave Nebinger" <dnebinger@joat.com> wrote the words:

> LDFLAGS typically come in the -llib and -Lpath variety and are used to
> ensure that additional libraries and paths are included in the link
> phase. You typically won't need to add these (which is probably why
> there is little if any reference in the gentoo doc).
> 
> Obviously there are more uses for LDFLAGS, but those above are used
> the most.
> 
> If you do need them you can set up your environment variables before
> doing the make process.  You can also use them on the command line ala
> "LDFLAGS=-llib make", etc.

Am I doing this correctly?  Because it's not working....

Sun Sep 04 09:42:47
/var/tmp/portage/pixie-1.4.1-r1/work/Pixie
 root $  ./configure LDFLAGS=-llib make --prefix=/usr/local
configure: WARNING: you should use --build, --host, --target
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for make-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C
compiler cannot create executables See `config.log' for more details.

Thanks,
Adrian


-- 
On The Fly Photography -:- Creation From Chaos

On The Fly Photography:  http://204EastSouth.com
Purchase from On The Fly:  http://204EastSouth.com/OTFStore.htm
The Cynical Libertarian Society:  http://www.204EastSouth.com/cls
-- 
gentoo-user@gentoo.org mailing list