On Jun 8, 2008, at 1:47 PM, Bengt Nilsson wrote:
I was wrong about building completed.
After removing smbd and re-make I got
Linking bin/smbd
ld:
Unresolved:
srvstr_push_fn2
make: *** [bin/smbd] Error 1
A quick summary of what I've discovered today:
The offending line (that generates the
On Mon, Jun 09, 2008 at 05:19:28PM -0700, Kai Lanz wrote:
is. I can't spend any more time on this today, but maybe this
update will suggest something to someone here.
If someone here can get me access to such an Ultrix box, I
will give it a try to fix it. But I need a login.
Volker
I was wrong about building completed.
After removing smbd and re-make I got
Linking bin/smbd
ld:
Unresolved:
srvstr_push_fn2
make: *** [bin/smbd] Error 1
7 jun 2008 kl. 13.28 skrev Bengt Nilsson:
I just commented out
/*
#define srvstr_push_fn2(fn_name, fn_line, base_ptr, dest, src,
Please know that I am NOT an experienced programmer,
In safe_string.h, there are 6 usages of
__unsafe_string_function_usage_here_size_t__
(I am not sure where trans2.c is coming into this.)
Anyway, to find out which one that fails, I created the single
prototype with
size_t
I just commented out
/*
#define srvstr_push_fn2(fn_name, fn_line, base_ptr, dest, src,
dest_len, flags) \
(CHECK_STRING_SIZE(dest, dest_len) \
? __unsafe_string_function_usage_here_size_t__6() \
: srvstr_push_fn(fn_name, fn_line, base_ptr, dest, src, dest_len,
flags))
*/
and got
I get the prorotype error (uint32 / uint32_t) in include/util_tdb.h
regardless of if I use cc or gcc, see [Samba] Failed building 3.0.30
for tru64 4.0F
If I modfy include/util_tdb.h changing uint32_t to uint32, and correct
the typo (TDB_BASE_OBJ) - (TDBBASE_OBJ) in the Makefile.in, . and
On Fri, Jun 06, 2008 at 02:16:20PM +0200, Bengt Nilsson wrote:
I get the prorotype error (uint32 / uint32_t) in include/util_tdb.h
regardless of if I use cc or gcc, see [Samba] Failed building 3.0.30
for tru64 4.0F
If I modfy include/util_tdb.h changing uint32_t to uint32, and correct
My system is OSF1 V4.0 1229 alpha, login message Digital UNIX
V4.0F (Rev. 1229)
I also have a OSF1 V5.1 2650 alpha, login message Compaq Tru64 UNIX
V5.1B (Rev. 2650).
I will try to see if it works better on the 5.1 system..
6 jun 2008 kl. 14.34 skrev Volker Lendecke:
On Fri, Jun 06, 2008
I tried ./configure + make on my 5.1 system and it worked fine.
So the problem is for the older Digital UNIX V4.0F system.
Do you have access to such a system?
6 jun 2008 kl. 14.34 skrev Volker Lendecke:
On Fri, Jun 06, 2008 at 02:16:20PM +0200, Bengt Nilsson wrote:
I get the prorotype error
On Fri, Jun 06, 2008 at 03:52:54PM +0200, Bengt Nilsson wrote:
I tried ./configure + make on my 5.1 system and it worked fine.
So the problem is for the older Digital UNIX V4.0F system.
Do you have access to such a system?
No, sorry :-)
Volker
pgpkQL3bit7wV.pgp
Description: PGP signature
--
On Jun 6, 2008, at 10:10 AM, Herb Lewis wrote:
try doing an nm on the suspected .o file and see if the reference
to the function is there. That will prove which file(s) is comes
from than maybe you can determine which function it comes from.
Thanks, but I've already done that; I used nm to
run script to capture all the following output
run gdb trans2.o then run the command x/400i (may need to change
the number of lines)
search for the offending function call and see where it says it
is in the file
Kai Lanz wrote:
On Jun 6, 2008, at 10:10 AM, Herb Lewis wrote:
try doing an nm
I'm trying to build 3.0.30 on Alpha/Tru64-4.0G. The configure step
works,
but make fails when it tries to link smbd:
Compiling popt/popt.c
Compiling popt/poptconfig.c
Compiling popt/popthelp.c
Compiling popt/poptparse.c
Linking bin/smbd
ld:
Unresolved:
13 matches
Mail list logo
