[bug #18397] static linking exits with error

<[email protected]>
Newsgroups gmane.network.mldonkey.bugs
Message-ID <[email protected]>
URL:
  <http://savannah.nongnu.org/bugs/?18397>

                 Summary: static linking exits with error
                 Project: mldonkey, a multi-networks file-sharing client
            Submitted by: White_FrosT
            Submitted on: Tuesday 11/28/2006 at 23:06
                Category: Core
                Severity: 3 - Normal
              Item Group: Compilation problem
                  Status: None
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 2.8.1.CVS
                 Release: 2.8.1
        Operating System: Linux
         Binaries Origin: CVS / Self compiled
                CPU type: Intel x86

    _______________________________________________________

Details:

I cannot compile a static core on FC6. Error:
---
ocamlopt.opt -inline 10 -linkall  -ccopt -static -o mlnet.static \
             unix.cmxa str.cmxa -ccopt " " -cclib "-lz  " -ccopt "-pthread"
\
          \
        -cclib "-lgd -lXpm -lX11 -ljpeg -lfontconfig -lfreetype -lpng12 -lz
-lm" -ccopt "-L/usr/lib"  \
        -cc 'g++ -g -O2' -ccopt '-fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer'  \
        -cclib -lmagic  \
        -I build    build/cdk.cmxa    build/magic.cmxa    build/common.cmxa  
 build/client.cmxa    build/core.cmxa    build/driver.cmxa   
src/daemon/common/commonMain.cmx
/usr/bin/ld: cannot find -lXpm
collect2: ld returned 1 exit status
Error during linking
make: *** [mlnet.static] Error 2
---

Could this be the solution:
http://bugs.centos.org/view.php?id=1518





    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?18397>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.