René Rebe wrote: > > The toolchain (gcc, ld, ...) default to look into system pathes that > include /lib, /usr/lib, the lib64 variants on multilib 64bit systems and > other > variants, (e.g. tls, notls, cpu optimization related dirs, etc) > yes thats what I expected, but in this case it does not look in /lib. Strange. I still don't understand why.
René Rebe wrote: > > You should not move the libraries around manually. > yes I know, but I was desperate ... :-D René Rebe wrote: > > /opt/*/lib... are not searched by default, which is why there are the > pkg-config files (or the old -config scripts) for packages to obtain > the correct pathes on a distribution - which varies between releases, > vendors (Fedora, Debian, etc.) and in T2 even between configurations. > > If the package configure does not include any support you would have > to patch it in (or use T2 automatics to inject it), but the configure > script might have a --with-imlib option to specify the patch. > no it does not have that. but I think its easy to add a patch in config and makefile with a -L Also for the above problem, a patch with -L/lib would probably help. But as you said: this shall be one of the system pathes. On the other hand: T2 is really impressive, how smoothly and automatically almost everything is working.=) (sometimes I miss some documentation...). I guess we are almost done with this package. Gerd -- View this message in context: http://www.nabble.com/.eh_frame-error-tp19744831p19783962.html Sent from the T2 mailing list archive at Nabble.com.
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe t2
