Ritu Kamboj wrote:
> Hi,
> 
> I was trying to compile using nightly script and am facing the following 
> issues....
> 
> 
> 1)  Missing autoconf:
> 
> checking whether autoconf is installed... no
> configure: error: Autoconf 2.58 or better is required.
>     Please make sure it is installed and in your PATH.
> *** Error code 1
> dmake: Warning: Target `install' not remade because of errors
> 
> 
> ...I saw that autoconf  2.61 is installed under 
> <workspace>/proto/root_i386/usr/bin directory ...do I need to add this 
> to my path......

no you need autoconf installed on the build machine, which is where
it should be. You did install at least Developer on this machine? I'd
think it should be there.

We previously had 2.59 so that should have satisfied configure, and
nightly does put /usr/sfw/bin in the path unless you override it,
so it does sound like you don't have it installed.

things the build needs should generally not be run directly from
the proto area as they may not run at all. In ON this is very true,
and in sfw though it can work it still might not (it might need
a library that's not on the build machine for example). Though I
know it's done in a few places.



> Current working directory 
> /home/build/mysqlBuild/ruby-integration-workspace/usr/src/cmd/apache2/mod_auth_gss
> 
> make: Fatal error in reader: Makefile, line 45: Read of include file 
> `../httpd-2.2.3/build/rules.mk' failed

It might be worth using bldenv to go there and build manually to figure
out why. I don't know why this might happen but perhaps you don't
have apache2 installed (which the build needs, but is also in Developer
I think).



> /home/build/mysqlBuild/ruby-integration-workspace/usr/src/cmd/cdrtools

>     /usr/ccs/bin/make -e CCOM=cc)
> 
> Segmentation Fault - core dumped
> 
> mksh: Fatal error: The command `(mach || uname -p || 
> true)2>/dev/null      | tr
> 
> '[A-Z]' '[a-z]' | tr ', /\\()"' ',------'' returned status `35584'

never seen that. cdrtools was one that liked to use 'cc' in the
path but it looks like you have the fix for that.  And no idea
why tr would core dump unless you're doing this in a non-C locale
(though nightly tries to force you into C).

BTW... so you're the one trying to use a fake 'build' account to
do the build? Since you're internal and using teamware I'll note that
that's not a good idea, since the account you use to bringover from
gets automatically added to the gate alias and sent mail. Which bounced
of course and so I redirect it to /dev/null but you should really
use your own account.

        Mike

Reply via email to