| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9
Comments:
<0> Ken|JLime: I'm currently at compiling gcc-cross-initial
<0> Ken|JLime: it will take some time until I'm there...
<1> ken|jlime where the libz.a coulnt bee find?
<2> freetype-2.1.10-r1 is the first to complain about missing libz.la
<2> libz.a i meant
<3> woglinde it wanted to find it under staging /lib/.libs/ but it was to be found under /lib
<0> why do you guys to refues to use grep?
<0> damn
<0> why do you guys refuse to use grep?
<2> zecke i moved the libz into staging and grepped the mentioned funtions out if them correctly but yet the apps "ignore" the libz library`s
<1> hm but I dont get why freetype needs staticle libz
<0> rob_w: that is "sticking something into someones arse"-tactic
<0> rob_w: all I ask for is analaysis...
<0> analyze the issues, at the end of the day we are engineers
<2> nm tmp/staging/arm-linux/lib/libz.a | grep inflate inflate.o:
<2> 0000035c T inflate
<1> rob_w and the symbol isnt in libz.so?
<0> /work/dev/donkey/build_6xx/tmp/staging/sh3-linux/lib/.libs/libz.a: No such file
<1> thats what me makes wonder
<0> the question everyone should himself
<0> I lib/.libs/ a sensible path
<0> is lib/.libs/a a sensible path
<0> Answer: No
<1> .libs never should go into staging
<1> i think
<0> Why does freetype think libz is in that path?
<0> Answer: I don't know!
<1> study the configure.log
<0> So to find an answer to the question is to look at config.log
<1> hm I should start build
<1> something
<0> use grep on *.la files
<0> this is no rocket science as well
<0> alternative b) is
<2> ..ask zecke
<0> send your disks+computers to the BMCO Forum at the AttilaStr. and I can do the post mortem for you
<3> haha
<0> use a free version of grep, e.g. GNU grep
<0> grep for libz in .la files
<1> lol
<0> :)
<1> hm do I need a new bitbake?
<0> woglinde: why?
<1> ${@base_read_file('/devel/arm/tmp/${distro}/staging/arm-linux/kernel/kernel-abiversion')}
<1> NOTE: exceptions.SyntaxError:EOL while scanning single-quoted string (line 1) while evaluating: ${SHLIBS}kernel (${KERNEL_VERSION})
<2> LDFLAGS_append = " -L. -lz"
<2>
<2> in zlib_1.2.3.bb
<0> rob_w: that is not what I haved asked for
<0> rob_w: either do what you are asked to or be quite
<2> i am learning , sorry
<0> randomly tossing garbage will piss me off
<0> rob_w: once again
<0> 1. identify the problem
<0> 2. analyze it
<0> 3. fix it
<0> at which point are you?
<2> 1. freetype looks for libs/.libs/libz.a
<0> why does it even look there
<0> we came to the conclusion it is not smart to look there
<2> ok
<0> 16:03 < rob_w> LDFLAGS_append = " -L. -lz"
<0> why should -L. or -lz lead to lib/.libs/?
<4> the gimp is actually pretty fast on ARM
<4> (if you have enough ram)
<0> koen: hehe, I just wanted to ask that
<0> koen: on my first Laptop (200mhz mmx Pentium) I used to open many, many, many pictures with gimp...
<4> locate jpg | xargs gimp
<4> that's what I used to do
<0> rob_w: so how do you want to continue?
<4> "one day I got bored and opened 20000 images in the gimp"
<2> ok i will clean freetype and rebuild to see the errror once more .. ok ?
<0> rob_w: you are starting to piss me off
<0> rob_w: why should the issue vanish now?
<2> hey dude , thats ok i ll go for myself now
<0> why do you refuse to do basic analysis?
<2> i just want to see hte error once more ok, so i can do your steps !!
<0> find . -name '*.la' -exec grep libs '{}' \;
<0> replace '.' with tmp/staging...
<0> rob_w: you can grep now as well...
<2> zecke, ok so this now shows me what ?
<0> rob_w: Well
<0> rob_w: as this is a developer channel, I will treat you like a developer
<0> We use a compiler to compile software
<0> these software use buildsystems to build the software
<0> GNU Autoconf/Automake allows to write portable software
<0> GNU libtool allows to create, use and load libraries in a portable manner
<0> now you configure freetype, which uses GNU auto-tools to configure itself?
<0> it tries to find the zlib?
<0> or it uses zlib indirectly
<0> this is the first question we need to answert
<0> GNU autoconf writes a config.log
<0> a protocol which describes the tests, results and actions it has done on configuring
<2> sure
<0> it can be used to analyse issues
<0> so findout if it mentions the zlib somehow?
<2> lemme check
<2> hecking for gzsetparams in -lz... yes
<2> checking zlib.h usability... yes
<2> checking zlib.h presence... yes
<2> checking for zlib.h... yes
<0> that is not config.log but anyway...
<2> i dont find a config.log inside the freetype ..
<0> "In aller Freundschaft"
<0> if someone tells you to open config.log and it is not present
<0> don't go for any other random file
<2> but i had a feeling to look into temp/log_do_configure ..
<2> also
<1> hehe find ./ -name "*-.log"
<1> ups
<1> hehe find ./ -name "*.log"
<1> log_do_configugre != config.loh
<1> log_do_configugre != config.log
<1> simple speech
<2> woglinde, that is new to me , sorry
<1> config.log is what configure produced
<1> log_do_configure is what oe produce
<1> d
<0> rob_w: check for config.log within the freetype directory
<2> i though those correspondent in some manner
<0> run.do_configure and log.do_configure correspondent
<0> config.log is created by the invocation of 'configure'
<1> yes because to see what configure says, normaly its on terminal and then gone
<0> hmm the freetype bbfiles looks fishy :}
<1> let me see
<1> hm no maintainer
<2> there is a freetype-2.1.10/builds/unix/config.log
<0> that is the one
<0> as ./configure is executed from within builds/unix
<2> i see
<0> To summarize
<0> We know that freetype checks for zlib and finds it
<1> hm no no
<0> looking at config.log will tell us where it finds it, and how it finds it
<1> there was problems with the normal-system libz
<1> so koen switched to the libz which is shipped with freetype
<1> thats the first configure.patch
<1> args
<1> koen are you around?
<4> I'm around
<1> koen what was excalty the problem with freetype an normal libz?
<4> the .libs thing
<4> so someone switched it to use the internal libz
<1> aeh?
<2> woglinde, but the configure patch looks to me as it doesnt change anything ,, it was like that before
<1> I thought it was something at runtime
<0> woglinde: one would have to specify --without-zlib to use the internal one
<0> woglinde: which we don't want to do for security concerns
<1> zecke yes
<4> koen@bitbake:~/OE/monotone/org.openembedded.dev/packages$ grep zlib freetype/freetype_2.2.1.bb
Return to
#oe
or
Go to some related
logs:
iptables xebian
#gentoo
def: oodalolly
#javascript
Package requirements (sm x11 xproto kbproto) were not met
#redhat
#openzaurus
bad TCP reclen rhel
chkroot gentoo
#perl
|
|