[wellylug] compiling troubles

[nic]

Hi Edouard

Without being in any way familiar with the specifics of you're seeing, two things strike 
me. First, your comments saying it used to work, and all libs are up to date. Possibly the 
update of the libraries actually broke something, so that paths are different. This is 
perhaps confirmed by the fact that you can't compile a basic driver.

The other thing is the warning that --datarootdir is being ignored. There are a whole 
bunch of similar instances mentioned on google, and generally seem to relate to the 
particular version of autoconf. So the two problems might go together. try looking at 
autoconf: maybe an update, or revert to a different version, or see if there's a 
compatibility mode.

Good luck

Nic C-L

Edouard Chalaron wrote:
> Hi all
> 
> I have been unable to recompile some source code that I had for a long
> time.
> I updated by subversion these sources and still can not compile.
> (Packages are not an option, the few I can find are not reliable,
> missing or deprecated libs)
> 
> For say, the autogen is working fine and configure is going fine too,
> however I managed to filter out some warning on the output
> of ./configure :
> 
> /bin/bash: ./config.rpath: No such file or directory
> cat: /etc/ld.so.conf.d/*.conf: No such file or directory
> cat: /etc/ld.so.conf.d/*.conf: No such file or directory
> config.status: WARNING:  po/Makefile.in.in seems to ignore the
> --datarootdir setting
> 
> That is a bit odd....
> That would be a first step.
> 
> Since ./configure says to me that all is Ok anyway and I go for a make,
> I just do it.
> 
> /usr/bin/ld: /usr/lib/libx264.a(common.o): relocation R_X86_64_32
> against `a local symbol' can not be used when making a shared object;
> recompile with -fPIC
> /usr/lib/libx264.a: could not read symbols: Bad value
> collect2: ld returned 1 exit status
> make[3]: *** [libquicktimehv.la] Error 1
> make[2]: *** [all-recursive] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
> 
> I sent the errors to the maintainers of the code, still waiting for an
> answer but, with my permanent condition of being a shit magnet, it seems
> that I am the only one.
> 
> So ... Is it related to the config warnings ? any suggestion, ideas ???
> anything ....the fPIC stuff is not in cause according to the
> developpers.
> X264 has been dowloaded and installed with making a deb package. No
> troubles...
> 
> Just for testing to eliminate all possible source of trouble I went to
> compile a really simple stuff (the driver for the wireless of my
> Presario V3000)... does not even compile.
> 
> Where I am really P...D off is that this code compiled out of the box
> recently.
> 
> Distribution is Feisty fawn for AMD64. All libs up to date, but may I
> miss some of them
> 
> Any help appreciated
> THanks
> Edouard
> 
> 
> 
> 
> 
> 
> 
>