Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 01 Jul 2015, 01:05
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Compiling
unable to compile scribus-1.4.0.rc6 in Puppy 5.2.5
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 1 of 1 Posts_count  
Author Message

Joined: 11 Dec 2007
Posts: 1426
Location: somewhere at the end of rainbow...

PostPosted: Thu 29 Dec 2011, 10:24    Post_subject:  unable to compile scribus-1.4.0.rc6 in Puppy 5.2.5  

Woof Woof!

Finally, after a lot of months, I get a part-time job

I need Scribus with multilingual support (included hyphenation and python scripting)

I started to compile in Puppy 5.2.5, using Qt-4.6.3 (tried also 4.8.0 but unsuccessfully)

first problem was with recognition of Python include dir
# cmake -DCMAKE_INCLUDE_PATH=/usr/include ..
-- Scribus 1.4.0.rc6 will be built to install into /usr/local
-- Machine: i486-linux-gnu, void pointer size: 4
-- Found target X86
-- Building for target i486-linux-gnu
-- Using standard ApplicationDataDir. You can change it with -DAPPLICATION_DATA_DIR
Qt4 Found OK
-- Building without Qt3 Support (GOOD)
ZLIB Library Found OK
Using PNG Library: /usr/lib/libpng.so
PNG Library Found OK
JPEG Library Found OK
TIFF Library Found OK
CMake Error at /share/cmake-2.6/Modules/FindPackageHandleStandardArgs.cmake:57 (MESSAGE):
Could NOT find PythonLibs (missing: PYTHON_INCLUDE_PATH)
Call Stack (most recent call first):
/share/cmake-2.6/Modules/FindPythonLibs.cmake:86 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:537 (FIND_PACKAGE)

-- Configuring incomplete, errors occurred!

not having time to further investigate, I edited cmake.lists to avoid to call python

this time compilation started, but, at 77% when gcc was ready to link executables, I get this very long error message:


any suggestion to identify problem and solve?

replace .co.cc with .info to get access to stuff I posted in forum
dropbox 2GB free
OpenOffice for Puppy Linux
Back to top
View user's profile Send_private_message Visit_website 

Joined: 07 Feb 2010
Posts: 2535
Location: wales

PostPosted: Sat 31 Dec 2011, 12:07    Post_subject:  

hi Dingo

can't help with the compiling, but this portable scribus seems to work on lupu. Don't know if it has all the multilingual stuff included, but worth a try http://sourceforge.net/projects/portable/files/Scribus%201.5.0.svn-C-C-T-F-C1.8.10/download


Tahrpup, built with trusty tahr packages http://murga-linux.com/puppy/viewtopic.php?t=96178
Quickpet_Precise, install popular apps quickly http://www.murga-linux.com/puppy/viewtopic.php?t=83642
Back to top
View user's profile Send_private_message 
Karl Godt

Joined: 20 Jun 2010
Posts: 4026
Location: Kiel,Germany

PostPosted: Wed 04 Jan 2012, 10:36    Post_subject:  

collect2: ld returned 1 exit status

the ld command is looking in the defined libraries for declarations like

if the library is not found OR the declaration was not compiled into the current library for not enabled at the compile time ,like --without-gss, of the library OR just not implemented into the code of the library-version
ld cannot put a tag into the output file .

The manpage of ld is rather long .

ld belongs to the "binutils" package together with better known binaries like strip and strings .

The binutils source compiles fine
as i am trying to find out to get grub legacy to compile for debian based pups
may have problems with grub legacy by debian for ext4 partitions .

Myself i am stuck at /usr/bin/objcopy not working as configure script for grub wants it to work .

Could not make it to work until today , even cp the racy522 objcopy to dpup . The same grub source compiled ok on racy522 .

The manpage of ld claims that there are some CFLAGS for get work finished and traced like

--unresolved-symbols=method [ignore-all ignore-in-shared-libs]
--verbose[=NUMBER] to see where the probs occure precisely
--warn-unresolved-symbol This option makes it generate a warning instead of an error
--disable-stdcall-fixup it will attempt
to do "fuzzy linking" by looking for another defined symbol that
differs only in the format of the symbol name (cdecl vs stdcall)
and will resolve that symbol by linking to the match
--print-map Print a link map to the standard output
--trace Print the names of the input files as ld processes them

You would likely need to recompile the needed libraries or try some of the above flags to create the binaries possibly not working in some functions .
Back to top
View user's profile Send_private_message 

Joined: 23 May 2007
Posts: 1123
Location: the australian mallee

PostPosted: Wed 18 Jan 2012, 21:21    Post_subject:  

Karl, have a look at the LD thread I put in programming and especially Jemimahs answer, it may be the same problem I am having, I'm going to have a go at a later as well as rebuilding the current.

Back to top
View user's profile Send_private_message Visit_website 
Display_posts:   Sort by:   
Page 1 of 1 Posts_count  
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Compiling
Jump to:  

You cannot attach files in this forum
You can download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0903s ][ Queries: 11 (0.0171s) ][ GZIP on ]