SEO

All,

As per the subject I'm trying [unsuccessfully!] to build Samba 3.0.1 on
an Open Server 5.0.6 system.

The system has 'gcc' installed, and configure decided to use that -
which is fine with me, unless you think different :-)

This is where things went horribly wrong...

---8<---

Compiling client/client.c
client/client.c: In function `do_get':
client/client.c:694: warning: passing arg 4 of `cli_getattrE' from
incompatible
pointer type
client/client.c: In function `do_put':
client/client.c:1070: warning: passing arg 4 of `cli_getattrE' from
incompatible
pointer type
client/client.c: In function `remote_completion':
client/client.c:2288: `PATH_MAX' undeclared (first use this function)
client/client.c:2288: (Each undeclared identifier is reported only once
client/client.c:2288: for each function it appears in.)
client/client.c: In function `do_host_query':
client/client.c:2669: warning: passing arg 1 of `list_servers' discards
`const'
from pointer target type
*** Error code 1 (bu21)

---8<---

Alternatively, if someone wants to save me all this trouble - does
anyone know of a pre-built binary distribution? (Yeah, yeah.. I know
Samba & SCO in the same sentence can provoke a more political
discussion these days).

Any help appreciated.

Thanks,

Stuart.

Stuart Marshall wrote:
> All,
>
> As per the subject I'm trying [unsuccessfully!] to build Samba 3.0.1 on
> an Open Server 5.0.6 system.
>
> The system has 'gcc' installed, and configure decided to use that -
> which is fine with me, unless you think different :-)
>
> This is where things went horribly wrong...
>
> ---8<---
>
> Compiling client/client.c
> client/client.c: In function `do_get':
> client/client.c:694: warning: passing arg 4 of `cli_getattrE' from
> incompatible
> pointer type
> client/client.c: In function `do_put':
> client/client.c:1070: warning: passing arg 4 of `cli_getattrE' from
> incompatible
> pointer type
> client/client.c: In function `remote_completion':
> client/client.c:2288: `PATH_MAX' undeclared (first use this function)
> client/client.c:2288: (Each undeclared identifier is reported only once
> client/client.c:2288: for each function it appears in.)
> client/client.c: In function `do_host_query':
> client/client.c:2669: warning: passing arg 1 of `list_servers' discards
> `const'
> from pointer target type
> *** Error code 1 (bu21)
>
> ---8<---
>

Never tried personally (and I'm not in the position to check now) but do
you have the

/usr/include/limits.h

file installed on your system ?

If not (but this __might__ be only an useless workaround), try by adding
the following in one of the samba's include file:

#ifndef PATH_MAX
#define PATH_MAX 1024
#endif

> Alternatively, if someone wants to save me all this trouble - does
> anyone know of a pre-built binary distribution? (Yeah, yeah.. I know
> Samba & SCO in the same sentence can provoke a more political
> discussion these days).

No, please, not today ! :-)

Best,
Roberto
--
Roberto Zini - Technical Support Manager - email:r.zini<AT>strhold.it
Technical Support Manager -- Strhold Evolution Division R.E. (ITALY)
---------------------------------------------------------------------
"Has anybody around here seen an aircraft carrier?"
(Pete "Maverick" Mitchell - Top Gun)

Roberto Zini wrote:
> Stuart Marshall wrote:

>> ---8<---
>>
>> Compiling client/client.c
>> client/client.c: In function `do_get':
>> client/client.c:694: warning: passing arg 4 of `cli_getattrE' from
>> incompatible
>> pointer type
>> client/client.c: In function `do_put':
>> client/client.c:1070: warning: passing arg 4 of `cli_getattrE' from
>> incompatible
>> pointer type
>> client/client.c: In function `remote_completion':
>> client/client.c:2288: `PATH_MAX' undeclared (first use this function)
>> client/client.c:2288: (Each undeclared identifier is reported only once
>> client/client.c:2288: for each function it appears in.)
>> client/client.c: In function `do_host_query':
>> client/client.c:2669: warning: passing arg 1 of `list_servers'
>> discards `const'
>> from pointer target type
>> *** Error code 1 (bu21)
>>
>> ---8<---
>>
> Never tried personally (and I'm not in the position to check now) but do
> you have the
>
> /usr/include/limits.h
>
> file installed on your system ?

Yes, that's already there...

> If not (but this __might__ be only an useless workaround), try by adding
> the following in one of the samba's include file:
>
> #ifndef PATH_MAX
> #define PATH_MAX 1024
> #endif

However, the PATH_MAX is defined as 256 not 1024. I've tried changing
it to 1024, but exactly the same thing happens unfortunately.

It is actually building the 'smbd' and 'nmbd' executables -
unfortunately they don't appear to work.

>> Alternatively, if someone wants to save me all this trouble - does
>> anyone know of a pre-built binary distribution? (Yeah, yeah.. I know
>> Samba & SCO in the same sentence can provoke a more political
>> discussion these days).
>
> No, please, not today ! :-)

:-)

What version of Samba does 5.0.7 come preinstalled with?

Thanks,

Stuart.

Stuart Marshall wrote:
> Roberto Zini wrote:
>
>> Stuart Marshall wrote:
>
>
>>> ---8<---
>>>
>>> Compiling client/client.c
>>> client/client.c: In function `do_get':
>>> client/client.c:694: warning: passing arg 4 of `cli_getattrE' from
>>> incompatible
>>> pointer type
>>> client/client.c: In function `do_put':
>>> client/client.c:1070: warning: passing arg 4 of `cli_getattrE' from
>>> incompatible
>>> pointer type
>>> client/client.c: In function `remote_completion':
>>> client/client.c:2288: `PATH_MAX' undeclared (first use this function)
>>> client/client.c:2288: (Each undeclared identifier is reported only once
>>> client/client.c:2288: for each function it appears in.)
>>> client/client.c: In function `do_host_query':
>>> client/client.c:2669: warning: passing arg 1 of `list_servers'
>>> discards `const'
>>> from pointer target type
>>> *** Error code 1 (bu21)
>>>
>>> ---8<---
>>>
>> Never tried personally (and I'm not in the position to check now) but
>> do you have the
>>
>> /usr/include/limits.h
>>
>> file installed on your system ?
>
>
> Yes, that's already there...

Are you in the position to check if the above actually gets included
into the *.c file ?

Also, what if you put the above "define" statements into the client.c file ?

>
>> If not (but this __might__ be only an useless workaround), try by
>> adding the following in one of the samba's include file:
>>
>> #ifndef PATH_MAX
>> #define PATH_MAX 1024 #endif
>
>
> However, the PATH_MAX is defined as 256 not 1024. I've tried changing
> it to 1024, but exactly the same thing happens unfortunately.
>

It's not a matter of value; it's a "I can't find the PATH_MAX
definition" issue.

> It is actually building the 'smbd' and 'nmbd' executables -
> unfortunately they don't appear to work.
>
>>> Alternatively, if someone wants to save me all this trouble - does
>>> anyone know of a pre-built binary distribution? (Yeah, yeah.. I know
>>> Samba & SCO in the same sentence can provoke a more political
>>> discussion these days).
>>
>>
>> No, please, not today ! :-)
>
>
> :-)
>
> What version of Samba does 5.0.7 come preinstalled with?
>

Samba 2.2.6 (as per the CD label).

Best,
Roberto
--
Roberto Zini - Technical Support Manager - email:r.zini<AT>strhold.it
Technical Support Manager -- Strhold Evolution Division R.E. (ITALY)
---------------------------------------------------------------------
"Has anybody around here seen an aircraft carrier?"
(Pete "Maverick" Mitchell - Top Gun)

In article <burdrk$ijjdk$1@ID-142465.news.uni-berlin.de>,
Stuart Marshall <stuart@spidersoft.co.uk> wrote:
>
>What version of Samba does 5.0.7 come preinstalled with?
>
Samba does not come pre-installed on SCO, there is the skunkware
site which currently (last time I heard) had 2.2.6, which from
reports I have heard has some issues on SCO).

I have several sites that have 2.0.7 which worked without
issue. 2.2.8a might be a version you can try and compile unless
you need the features of 3.0.


Dave

Roberto Zini <rob@robnothere.com> wrote in message news:<burifn$2cj$1@newsread.albacom.net>...
> Stuart Marshall wrote:
> > Roberto Zini wrote:
> >
> >> Stuart Marshall wrote:
> >
> >
> >>> ---8<---
> >>>
> >>> Compiling client/client.c
> >>> client/client.c: In function `do_get':
> >>> client/client.c:694: warning: passing arg 4 of `cli_getattrE' from
> >>> incompatible
> >>> pointer type
> >>> client/client.c: In function `do_put':
> >>> client/client.c:1070: warning: passing arg 4 of `cli_getattrE' from
> >>> incompatible
> >>> pointer type
> >>> client/client.c: In function `remote_completion':
> >>> client/client.c:2288: `PATH_MAX' undeclared (first use this function)
> >>> client/client.c:2288: (Each undeclared identifier is reported only once
> >>> client/client.c:2288: for each function it appears in.)
> >>> client/client.c: In function `do_host_query':
> >>> client/client.c:2669: warning: passing arg 1 of `list_servers'
> >>> discards `const'
> >>> from pointer target type
> >>> *** Error code 1 (bu21)
> >>>
> >>> ---8<---
> >>>
> >> Never tried personally (and I'm not in the position to check now) but
> >> do you have the
> >>
> >> /usr/include/limits.h
> >>
> >> file installed on your system ?
> >
> >
> > Yes, that's already there...
>
> Are you in the position to check if the above actually gets included
> into the *.c file ?
>
> Also, what if you put the above "define" statements into the client.c file ?
>
> >
> >> If not (but this __might__ be only an useless workaround), try by
> >> adding the following in one of the samba's include file:
> >>
> >> #ifndef PATH_MAX
> >> #define PATH_MAX 1024 #endif
> >
> >
> > However, the PATH_MAX is defined as 256 not 1024. I've tried changing
> > it to 1024, but exactly the same thing happens unfortunately.
> >
>
> It's not a matter of value; it's a "I can't find the PATH_MAX
> definition" issue.
>
> > It is actually building the 'smbd' and 'nmbd' executables -
> > unfortunately they don't appear to work.
> >
> >>> Alternatively, if someone wants to save me all this trouble - does
> >>> anyone know of a pre-built binary distribution? (Yeah, yeah.. I know
> >>> Samba & SCO in the same sentence can provoke a more political
> >>> discussion these days).
> >>
> >>
> >> No, please, not today ! :-)
> >
> >
> > :-)
> >
> > What version of Samba does 5.0.7 come preinstalled with?
> >
>
> Samba 2.2.6 (as per the CD label).
>
> Best,
> Roberto


I built 2.2.8a about 6 months ago here:
http://www.aljex.com/bkw/index.html#samba

And now there is a sco-built 2.2.8 that is part of this cd image:
ftp://ftp.sco.com/pub/openserver5/50...pp1CDimage.iso

Dave Gresham typed (on Fri, Jan 23, 2004 at 11:47:30PM +0000):
| In article <burdrk$ijjdk$1@ID-142465.news.uni-berlin.de>,
| Stuart Marshall <stuart@spidersoft.co.uk> wrote:
| >
| >What version of Samba does 5.0.7 come preinstalled with?
| >
| Samba does not come pre-installed on SCO, there is the skunkware
| site which currently (last time I heard) had 2.2.6, which from
| reports I have heard has some issues on SCO).
|
| I have several sites that have 2.0.7 which worked without
| issue. 2.2.8a might be a version you can try and compile unless
| you need the features of 3.0.

Sites that have 2.0.7? You mean 5.0.7?

If you don't know what you're talking about, best not to talk. Samba
2.2.6 is on the 5.0.7 distribution CDs. There's no need to get it from
Skunkware.


--
JP

In article <20040124012022.GA29375@jpradley.jpr.com>,
Jean-Pierre Radley <jpr@jpr.com> wrote:
>Dave Gresham typed (on Fri, Jan 23, 2004 at 11:47:30PM +0000):
>| In article <burdrk$ijjdk$1@ID-142465.news.uni-berlin.de>,
>| Stuart Marshall <stuart@spidersoft.co.uk> wrote:
>| >
>| >What version of Samba does 5.0.7 come preinstalled with?
>| >
>| Samba does not come pre-installed on SCO, there is the skunkware
>| site which currently (last time I heard) had 2.2.6, which from
>| reports I have heard has some issues on SCO).
>|
>| I have several sites that have 2.0.7 which worked without
>| issue. 2.2.8a might be a version you can try and compile unless
>| you need the features of 3.0.
>
>Sites that have 2.0.7? You mean 5.0.7?
>
>If you don't know what you're talking about, best not to talk. Samba
>2.2.6 is on the 5.0.7 distribution CDs. There's no need to get it from
>Skunkware.
>
>
Yes, it is best that you don't talk if you don't know what you
are talking about. Samba version 2.0.7 is a stable enviornment
on the systems that I work with.

dave

On Fri, 23 Jan 2004 10:33:49 +0000, Stuart Marshall
<stuart@spidersoft.co.uk> wrote:

>All,
>
>As per the subject I'm trying [unsuccessfully!] to build Samba 3.0.1 on
>an Open Server 5.0.6 system.
>
>The system has 'gcc' installed, and configure decided to use that -
>which is fine with me, unless you think different :-)
>
I gave up about a year ago trying to compile any recent version of
Samba. I found that once the 5.0.6a patch was installed on SCO Samba
and some other programs were no longer able to compile. I had posted
a few times here but no answers were found. I don't recall the error
messages I saw but I am so fed up with SCO and their lawsuits I am
migrating all of my systems off of SCO as quickly as the $$$ permits.

Gary Quiring

On Fri, 23 Jan 2004 10:33:49 +0000, Stuart Marshall
<stuart@spidersoft.co.uk> wrote:

>All,
>
>As per the subject I'm trying [unsuccessfully!] to build Samba 3.0.1 on
>an Open Server 5.0.6 system.
>
>The system has 'gcc' installed, and configure decided to use that -
>which is fine with me, unless you think different :-)
>
>This is where things went horribly wrong...

Good. I'm sure the Samba team will be very pleased at your failure to
use their code in the OS of a scumbag caompany that is trying it's
damndest to kill their project despite profiting from their work.

You do realise of course that you are violating the licence under
which Samba is distributed by attempting to build it for SCO? You have
agreed to abide by your ownerH^H^H^H^H^OS supplier's terms. Since they
claim the GPL is invalid, it's obviously incompatible with their
tired, worthless products.

--
FyRE < "War: The way Americans learn geography" >