|
From: Naveen K. <g_n...@ya...> - 2004-12-14 20:43:02
|
Hi folks, I have attempting to build valgrind on Solaris-x86. I am having problems during linking. I get the error vg_main.o: In function `get_file_clo': /home/msat/port/valgrind/coregrind/vg_main.c:524: undefined reference to `vgPlain_open64' There are similar errors for vgPlain_getrlimit64 & vgPlain_setrlimit64. Also I get these statements(warnings ?) from ld. /usr/local/bin/ld: section .rodata [00000160 -> 0001d17f] overlaps section .text [00000000 -> 0005be7f] /usr/local/bin/ld: section .rel.got [0001d180 -> 0001d18f] overlaps section .text [00000000 -> 0005be7f] /usr/local/bin/ld: section .rel.plt [0001d190 -> 0001d32f] overlaps section .text [00000000 -> 0005be7f] /usr/local/bin/ld: section .rel.bss [0001d330 -> 0001d347] overlaps section .text [00000000 -> 0005be7f] /usr/local/bin/ld: section .interp [0001d348 -> 0001d35a] overlaps section .text [00000000 -> 0005be7f] /usr/local/bin/ld: section .gnu.version_d [0001d35c -> 0001d393] overlaps section .text [00000000 -> 0005be7f] /usr/local/bin/ld: section .gnu.version [0001d394 -> 0001dbb3] overlaps section .text [00000000 -> 0005be7f] /usr/local/bin/ld: section .gnu.version_r [0001dbb4 -> 0001dc33] overlaps section .text [00000000 -> 0005be7f] /usr/local/bin/ld: section .dynsym [0001dc34 -> 00021d33] overlaps section .text [00000000 -> 0005be7f] /usr/local/bin/ld: section .dynstr [00021d34 -> 00027bd8] overlaps section .text [00000000 -> 0005be7f] /usr/local/bin/ld: section .hash [00027bdc -> 00029c3f] overlaps section .text [00000000 -> 0005be7f] Can somebody point me in the right direction ? Thanks Naveen __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Nicholas N. <nj...@ca...> - 2004-12-14 23:37:55
|
On Tue, 14 Dec 2004, Naveen Kumar wrote: > I have attempting to build valgrind on Solaris-x86. Valgrind doesn't work on x86/Solaris, only x86/linux at the moment. Did it not fail on your x86/Solaris machine at configure time? N |
|
From: Jeremy F. <je...@go...> - 2004-12-15 02:25:10
|
On Tue, 2004-12-14 at 23:37 +0000, Nicholas Nethercote wrote: > On Tue, 14 Dec 2004, Naveen Kumar wrote: > > > I have attempting to build valgrind on Solaris-x86. > > Valgrind doesn't work on x86/Solaris, only x86/linux at the moment. > Did it not fail on your x86/Solaris machine at configure time? He's taking the advice it gave him literally, and doing a port. J |
|
From: Jeremy F. <je...@go...> - 2004-12-15 08:50:29
|
On Tue, 2004-12-14 at 12:42 -0800, Naveen Kumar wrote: > Hi folks, > I have attempting to build valgrind on Solaris-x86. > I am having problems during linking. I get the error > > vg_main.o: In function `get_file_clo': > /home/msat/port/valgrind/coregrind/vg_main.c:524: > undefined reference to `vgPlain_open64' > > There are similar errors for vgPlain_getrlimit64 & > vgPlain_setrlimit64. These are linux syscalls. You're going to need to work out what the appropriate syscalls for Solaris are. You're also going to need to create a coregrind/x86-solaris, and put *.S files in there. A definition of VG_(do_syscall) will be the first priority. A lot of vg_mylibc.c is also Linux-specific, so you'll need to come up with a Solaris-specific version. > > Also I get these statements(warnings ?) from ld. > > /usr/local/bin/ld: section .rodata [00000160 -> > 0001d17f] overlaps section .text [00000000 -> > 0005be7f] > [...] > Can somebody point me in the right direction ? You're going to have to look into how Solaris/x86 lays out the address space for a process, and adjust the generation of coregrind/x86/stage2.lds accordingly. J |
|
From: Naveen K. <g_n...@ya...> - 2004-12-15 15:44:43
|
J, I am slightly consfused. VG_(open) expands to vgPlain_open does it not ? vg_mylibc.c defines a VG_(open)(...) i.e vgPlain_open(...) so the linker shouldn't complain that VG_(open) in vg_main.c is not found. I understand that the implementation on VG_(open) wont work for solaris but shouldn't it be able to atleast link everything. I did an "nm" on vg_mylibc.o for open this is what I get. nm vg_mylibc.o | grep open 00001a74 T vgPlain_open so vgPlain_open is present but where does vgPlain_open64 come from ? Naveen --- Jeremy Fitzhardinge <je...@go...> wrote: > On Tue, 2004-12-14 at 12:42 -0800, Naveen Kumar > wrote: > > Hi folks, > > I have attempting to build valgrind on > Solaris-x86. > > I am having problems during linking. I get the > error > > > > vg_main.o: In function `get_file_clo': > > /home/msat/port/valgrind/coregrind/vg_main.c:524: > > undefined reference to `vgPlain_open64' > > > > There are similar errors for vgPlain_getrlimit64 & > > vgPlain_setrlimit64. > > These are linux syscalls. You're going to need to > work out what the > appropriate syscalls for Solaris are. You're also > going to need to > create a coregrind/x86-solaris, and put *.S files in > there. A > definition of VG_(do_syscall) will be the first > priority. A lot of > vg_mylibc.c is also Linux-specific, so you'll need > to come up with a > Solaris-specific version. > > > > > Also I get these statements(warnings ?) from ld. > > > > /usr/local/bin/ld: section .rodata [00000160 -> > > 0001d17f] overlaps section .text [00000000 -> > > 0005be7f] > > [...] > > Can somebody point me in the right direction ? > > You're going to have to look into how Solaris/x86 > lays out the address > space for a process, and adjust the generation of > coregrind/x86/stage2.lds accordingly. > > J > > __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com |
|
From: Tom H. <th...@cy...> - 2004-12-15 16:08:51
|
In message <200...@we...>
Naveen Kumar <g_n...@ya...> wrote:
> so vgPlain_open is present but where does
> vgPlain_open64 come from ?
You have probably included a system header file that redefines
open as open64.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Naveen K. <g_n...@ya...> - 2004-12-15 16:15:51
|
Tom you were right. Thanks. Naveen --- Tom Hughes <th...@cy...> wrote: > In message > <200...@we...> > Naveen Kumar <g_n...@ya...> wrote: > > > so vgPlain_open is present but where does > > vgPlain_open64 come from ? > > You have probably included a system header file that > redefines > open as open64. > > Tom > > -- > Tom Hughes (th...@cy...) > Software Engineer, Cyberscience Corporation > http://www.cyberscience.com/ > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT > Products from real users. > Discover which products truly live up to the hype. > Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo |