Login | Register
My pages Projects Community openCollabNet

Discussions > dev > FSVS configure having hard coded paths

fsvs
Discussion topic

Hide all messages in topic

All messages in topic

Re: FSVS configure having hard coded paths

Author pmarek
Full name P.Marek
Date 2010-06-02 00:21:13 PDT
Message Hello Steve,


> I have added the link in the TARGET_LDFLAGS and the linkage fails with
...
> /usr/bin/ld: warning: libm.so.0, needed by
> /home/countcobolt/8.​09.2/staging_dir/i38​6/usr/lib/libsvn_sub​r-1.so, not
> found (try using -rpath or -rpath-link)
...
> When I add
> TARGET_LDFLAGS+=-Wl,​-rpath-link="/home/c​ountcobolt/8.09.2/st​aging_dir/toolchain-​i386_gcc4.1.2/lib/"
>
> To the make file the output becomes:
> Link fsvs
> /usr/lib/gcc/i686-re​dhat-linux/4.4.3/../​../../crt1.o: In function `_start':
> (.text+0xc): undefined reference to `__libc_csu_fini'
> /usr/lib/gcc/i686-re​dhat-linux/4.4.3/../​../../crt1.o: In function `_start':
> (.text+0x11): undefined reference to `__libc_csu_init'
> /usr/lib/gcc/i686-re​dhat-linux/4.4.3/../​../../crt1.o: In function `_start':
> (.text+0x1d): undefined reference to `__libc_start_main'
> build.o: In function `delay__work':
> build.c:(.text+0x70): undefined reference to `__ctype_b_loc'
> cp_mv.o: In function `cm___string_to_rev_path':
> cp_mv.c:(.text+0x799): undefined reference to `__ctype_b_loc'
> hash_ops.o: In function `hsh___new_bare':
> hash_ops.c:(.text+0x689): undefined reference to `__ctype_b_loc'
> helper.o: In function `hlp___get_conv_handle':
> helper.c:(.text+0x712): undefined reference to `iconv_open'
> helper.o: In function `hlp__chrooter':
...
> The strange thing is that it is linking towards the regular
> /usr/lib/gcc/i686-re​dhat-linux/4.4.3/ and not the i486 one
>
> Any help appreciated
Please edit the Makefile, and make sure that -liconv is given
somewhere - that wouldn't help for the __ctype_ functions, but
is a first step.

Please try to fix the various -I and -L paths that are set in the
first few lines, too - maybe that helps a bit.


But why it tries to use 686 and not the 486 paths, and doesn't
find the symbols I'm a bit lost ...


Regards,

Phil


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: FSVS configure having hard coded paths

Author cobolt
Full name steve caster
Date 2010-06-01 11:46:10 PDT
Message HI all

I have added the link in the TARGET_LDFLAGS and the linkage fails with

url.c:887: warning: 'svn_ra_open' is deprecated (declared at
/usr/include/subvers​ion-1/svn_ra.h:627)
 CC waa.c
 CC warnings.c
 Link fsvs
/usr/bin/ld: warning: libm.so.0, needed by
/home/countcobolt/8.​09.2/staging_dir/i38​6/usr/lib/libsvn_sub​r-1.so, not
found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libcrypt.so.0, needed by
/home/countcobolt/8.​09.2/staging_dir/i38​6/usr/lib/libsvn_sub​r-1.so, not
found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: ld-uClibc.so.0, needed by
/home/countcobolt/8.​09.2/staging_dir/too​lchain-i386_gcc4.1.2​/lib/libc.so,
not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libc.so.6, needed by /lib/libpthread.so.0, may
conflict with libc.so.0
/usr/bin/ld: errno: TLS definition in /lib/libc.so.6 section .tbss
mismatches non-TLS definition in
/home/countcobolt/8.​09.2/staging_dir/too​lchain-i386_gcc4.1.2​/lib/libc.so
section .bss
/lib/libc.so.6: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[5]: *** [fsvs] Error 1
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/home/countcobolt/8​.09.2/build_dir/i386​/fsvs-1.1.17'
make[3]: *** [/home/countcobolt/8​.09.2/build_dir/i386​/fsvs-1.1.17/.built]​
Error 2
make[3]: Leaving directory `/home/countcobolt/8​.09.2/package/fsvs'
make[2]: *** [package/fsvs/compile] Error 2
make[2]: Leaving directory `/home/countcobolt/8.09.2'
make[1]: ***
[/home/countcobolt/8​.09.2/staging_dir/i3​86/stamp/.package_co​mpile] Error 2
make[1]: Leaving directory `/home/countcobolt/8.09.2'
make: *** [world] Error 2

When I add
TARGET_LDFLAGS+=-Wl,​-rpath-link="/home/c​ountcobolt/8.09.2/st​aging_dir/toolchain-​i386_gcc4.1.2/lib/"

To the make file the output becomes:
 Link fsvs
/usr/lib/gcc/i686-re​dhat-linux/4.4.3/../​../../crt1.o: In function `_start':
(.text+0xc): undefined reference to `__libc_csu_fini'
/usr/lib/gcc/i686-re​dhat-linux/4.4.3/../​../../crt1.o: In function `_start':
(.text+0x11): undefined reference to `__libc_csu_init'
/usr/lib/gcc/i686-re​dhat-linux/4.4.3/../​../../crt1.o: In function `_start':
(.text+0x1d): undefined reference to `__libc_start_main'
build.o: In function `delay__work':
build.c:(.text+0x70): undefined reference to `__ctype_b_loc'
cp_mv.o: In function `cm___string_to_rev_path':
cp_mv.c:(.text+0x799): undefined reference to `__ctype_b_loc'
hash_ops.o: In function `hsh___new_bare':
hash_ops.c:(.text+0x689): undefined reference to `__ctype_b_loc'
helper.o: In function `hlp___get_conv_handle':
helper.c:(.text+0x712): undefined reference to `iconv_open'
helper.o: In function `hlp__chrooter':
helper.c:(.text+0x8ad): undefined reference to `dlopen'
helper.c:(.text+0x926): undefined reference to `dlopen'
helper.c:(.text+0x987): undefined reference to `iconv_open'
helper.o: In function `hlp__safe_print':
helper.c:(.text+0x165e): undefined reference to `__ctype_b_loc'
helper.o: In function `hlp__string_from_filep':
helper.c:(.text+0x17c5): undefined reference to `__ctype_b_loc'
helper.c:(.text+0x1815): undefined reference to `__ctype_b_loc'
helper.o: In function `hlp___do_convert':
helper.c:(.text+0x2451): undefined reference to `iconv'
helper.c:(.text+0x2546): undefined reference to `iconv'
ignore.o: In function `ign___init_pattern_into':
ignore.c:(.text+0xddb): undefined reference to `__ctype_b_loc'
log.o: In function `log(long double,...)(char,...)(int, void,...)(long
double)':
log.c:(.text+0x9b1): undefined reference to `_IO_putc'
options.o: In function `opt__variable_from_option':
options.c:(.text+0x6): undefined reference to `__ctype_toupper_loc'
options.o: In function `opt__parse_option':
options.c:(.text+0x42): undefined reference to `__ctype_b_loc'
options.o: In function `opt__parse':
options.c:(.text+0xbb): undefined reference to `__ctype_b_loc'
options.o: In function `opt__load_env':
options.c:(.text+0x266): undefined reference to `__ctype_tolower_loc'
options.o: In function `opt__load_settings':
options.c:(.text+0x438): undefined reference to `__ctype_b_loc'
update.o: In function `up__parse_prop':
update.c:(.text+0x1438): undefined reference to `__ctype_b_loc'
update.c:(.text+0x1507): undefined reference to `__ctype_b_loc'
url.o: In function `url__load_list':
url.c:(.text+0x1b51): undefined reference to `__ctype_b_loc'
url.c:(.text+0x1cd5): undefined reference to `__ctype_b_loc'
waa.o:waa.c:(.text+0x20aa): more undefined references to `__ctype_b_loc'
follow
waa.o: In function `waa__find_common_base2':
waa.c:(.text+0x386a): undefined reference to `rindex'
collect2: ld returned 1 exit status
make[5]: *** [fsvs] Error 1
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/home/countcobolt/8​.09.2/build_dir/i386​/fsvs-1.1.17'
make[3]: *** [/home/countcobolt/8​.09.2/build_dir/i386​/fsvs-1.1.17/.built]​
Error 2
make[3]: Leaving directory `/home/countcobolt/8​.09.2/package/fsvs'
make[2]: *** [package/fsvs/compile] Error 2
make[2]: Leaving directory `/home/countcobolt/8.09.2'
make[1]: ***
[/home/countcobolt/8​.09.2/staging_dir/i3​86/stamp/.package_co​mpile] Error 2
make[1]: Leaving directory `/home/countcobolt/8.09.2'
make: *** [world] Error 2

The strange thing is that it is linking towards the regular
/usr/lib/gcc/i686-re​dhat-linux/4.4.3/ and not the i486 one

Any help appreciated

Thx
S.
 
----------------original message-----------------
From: "Philipp Marek"
To: "steve caster" steve at c2root dot be
CC: "dev" dev at fsvs dot tigris dot org
Date: Wed, 26 May 2010 11:22:27 +0200 (CEST)
--------------------​--------------------​---------
 
 
> Hello Steve!
>
>> I am trying to port fsvs to openwrt ...
>> I found
>> LIBDIRS= /usr/local/lib in the configure script.
>> Maybe somone could help me
>> out by explaining me how this can be changed so
>> fsvs is not having hardcoded
>> links in the configure.
> Well, the configure script takes parameters - see
> ./configure --help
>
> for a list.
>
> There are parameters for the APR and subversion include
> directories; the other paths for the C compiler should
> be settable by having them defined for the configure
> script, like this:
> CFLAGS="-I/usr/include -I/opt/include" LDFLAGS="/usr/lib/" ./configure
> again with parameters.
>
> --with-aprinc=...
> --with-svninc=...
> --with-aprlib=...
> --with-svnlib=...
>
>
>> I am working on 1.1.17 as 1.2.2 fails on stating it
>> has an invalid valgrind
>> (another flacky journey ahead :D).
> If the configure script just says "No compatible valgrind
> version found", you can safely ignore that.
>
> If fact, valgrind is only used for debugging.
>
>> So any help is appreciate.
> I hope that helps a bit.
>
> If you encounter further problems, just ask!
>
>
> Regards,
>
> Phil
>
>
> --
> Versioning your /etc, /home or even your whole installation?
> Try fsvs (fsvs.tigris.org)!
>
>

Re: FSVS configure having hard coded paths

Author pmarek
Full name P.Marek
Date 2010-05-26 02:22:32 PDT
Message Hello Steve!

> I am trying to port fsvs to openwrt ...
> I found
> LIBDIRS= /usr/local/lib in the configure script.
> Maybe somone could help me
> out by explaining me how this can be changed so
> fsvs is not having hardcoded
> links in the configure.
Well, the configure script takes parameters - see
    ./configure --help

for a list.

There are parameters for the APR and subversion include
directories; the other paths for the C compiler should
be settable by having them defined for the configure
script, like this:
    CFLAGS="-I/usr/include -I/opt/include" LDFLAGS="/usr/lib/" ./configure
again with parameters.

  --with-aprinc=...
  --with-svninc=...
  --with-aprlib=...
  --with-svnlib=...


> I am working on 1.1.17 as 1.2.2 fails on stating it
> has an invalid valgrind
> (another flacky journey ahead :D).
If the configure script just says "No compatible valgrind
version found", you can safely ignore that.

If fact, valgrind is only used for debugging.

> So any help is appreciate.
I hope that helps a bit.

If you encounter further problems, just ask!


Regards,

Phil


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

FSVS configure having hard coded paths

Author cobolt
Full name steve caster
Date 2010-05-26 01:23:05 PDT
Message Hi all

I am trying to port fsvs to openwrt as they have all the other prerequisites
available for fsvs and new routers are capable of adding storage devices. I
am currently working on a soekris platform for this (x86 based systems).

I spend the whole weekend trying to compile version 1.1.17 on it and
apparently it fails due to the fact that there are references to libdirs and
inc dirs hardcoded in the configure script.

I am not a programmer and are only making my first steps in porting
packages, so figuring out the configure script was quite a journey. I found
LIBDIRS= /usr/local/lib in the configure script. Maybe somone could help me
out by explaining me how this can be changed so fsvs is not having hardcoded
links in the configure.

I am working on 1.1.17 as 1.2.2 fails on stating it has an invalid valgrind
(another flacky journey ahead :D).

So any help is appreciate. Of course I will be sharing these binaries once
they are properly compiling.

 

best regards

 

Steve
Attachments
Messages per page: