[Lunar-bugs] [support] poppler module

[Lunar bug reports list]

 Project:      lunar-linux
 ID:           
 Version:      <none>
 Component:    moonbase (modules)
 Category:     support requests
 Priority:     normal
 Assigned to:  <unassigned>
 Reported by:  dveatch
 Updated by:   v3rt1g0
 Status:       active
 Attachment:   http://lunar-linux.org/files/issues/poppler-compile.txt.bz2 (9.21 KB)

I decided to throw a quick module together myself to give this a test. 
I only created a DETAILS file (no BUILD, etc)


          MODULE=poppler
         VERSION=0.3.3
          SOURCE=$MODULE-$VERSION.tar.gz
      SOURCE_URL=http://$MODULE.freedesktop.org/
      SOURCE_VFY=sha1:4dd3e060815a307dfb217dbe7dd7d52c7f688edf
        WEB_SITE=http://poppler.freedesktop.org/
         ENTERED=20050730
         UPDATED=20050730
           SHORT=""

cat 

v3rt1g0



Previous comments:
------------------------------------------------------------------------

Sun, 07/31/2005 - 17:08 : dveatch

Attachment: http://lunar-linux.org/files/issues/poppler-0.3.3.bz2 (8.05 KB)

I was helping a new Lunar user debug a module (poppler) he was making.
The lin would fail with;

./poppler/.libs/libpoppler.so: undefined reference to `operator
new[](unsigned)'

The thing is it would ./configure and make fine from the cli but not
from lin. In fact from cli I could use just about any combination of
switches with any problems at all. It doesn't need a BUILD, just the
standard tree steps. So to answer that I made a BUILD and it still
fails. 

I've seen this once or twice before but cannot find, or remember or
google answer the solution to this. Well google had something sort of
related about g++ versus gcc in the Makefile and that it should be g++
(IIRC). So I checked the Makefile after the ./configure and it was
correct.

Any pointers?

-- 
View: http://lunar-linux.org/?q=node/view/923
Edit: http://lunar-linux.org/?q=project/comments/add/923