Re: buildworld error v1.8 - undefined reference to `EVP_sha256'

2007-02-01 Thread Sascha Wildner

j s wrote:

Here's the error.  I have attempted building several times including
from a cleaned /usr/src and cvsup with tag=.  and
tag=DragonFly_RELEASE_1_8_Slip

cc -O -pipe -mtune=pentiumpro
-I/usr/src/secure/libexec/sftp-server/../../lib/libssh
-I/usr/src/secure/libexec/sftp-server/../../../crypto/openssh-4
-L/usr/pkg/lib -o sftp-server sftp-server.o sftp-common.o -lssh
-lcrypto
/usr/obj/usr/src/world_i386/usr/lib/libssh.so: undefined reference to
`EVP_sha256'
*** Error code 1

Stop in /usr/src/secure/libexec/sftp-server.
*** Error code 1

I've modified make.conf to avoid building certain subsystems:

NO_BIND=true# do not build BIND
NO_GAMES=   true# do not enter the games subdirectory
NO_I4B= true# do not build isdn4bsd package
NO_LPR= true# do not build lpr and related programs
NO_SENDMAIL=true# do not build sendmail and related programs


Don't know where to go with this and a suggestion would be very helpful.


Hm, how do you build? Do you have other settings in make.conf?

I'm not able to reproduce this using the settings you gave.

Sascha

--
http://yoyodyne.ath.cx


Re: buildworld error v1.8 - undefined reference to `EVP_sha256'

2007-02-01 Thread YONETANI Tomokazu
On Wed, Jan 31, 2007 at 03:10:21PM -0800, j s wrote:
 cc -O -pipe -mtune=pentiumpro
 -I/usr/src/secure/libexec/sftp-server/../../lib/libssh
 -I/usr/src/secure/libexec/sftp-server/../../../crypto/openssh-4
 -L/usr/pkg/lib -o sftp-server sftp-server.o sftp-common.o -lssh


You have something similar to this

LDFLAGS=-L/usr/pkg/lib

in /etc/make.conf?  Try commenting out, or use a custom make.conf
only for {build,install}{kernel,world} to avoid this.  You can use
$__MAKE_CONF to switch make.conf files:

cd /usr/src
env __MAKE_CONF=/etc/src.conf make buildworld

Cheers.


Re: buildworld error v1.8 - undefined reference to `EVP_sha256'

2007-02-01 Thread j s

On 2/1/07, Sascha Wildner [EMAIL PROTECTED] wrote:

j s wrote:
 Here's the error.  I have attempted building several times including
 from a cleaned /usr/src and cvsup with tag=.  and
 tag=DragonFly_RELEASE_1_8_Slip


snip


Hm, how do you build? Do you have other settings in make.conf?

I'm not able to reproduce this using the settings you gave.

Sascha


Hi Sascha,
Thanks for taking a look. I'm following the man build instructions.
I started with an empty /usr/src  cvsup -g -L 2 file,   The latest
cvsup I had set tag=DragonFly_RELEASE_1_8_Slip, then proceeded
directly to make buildworld.

I'm also attempting the upgrade from DragonFly 1.7.0-DEVELOPMENT #0.

I've set LDFLAGS=-L/usr/pkg/lib, CPPFLAGS=-I/usr/pkg/include and
LD_LIBRARY_PATH=/usr/pkg/lib:/usr/local/lib:/usr/lib in the
environment.

I didn't bother sending any more make.conf content because it is
pretty standard install config.  However, here you go just in case:

# $FreeBSD: src/etc/defaults/make.conf,v 1.97.2.80 2003/02/15 16:34:56
trhodes Exp $
# $DragonFly: src/etc/defaults/make.conf,v 1.17 2006/07/02 16:03:42
swildner Exp $
#
#
#CPUTYPE=i686
#NO_CPU_CFLAGS= true# Don't add -march=cpu to CFLAGS automatically
#NO_CPU_COPTFLAGS=true  # Don't add -march=cpu to COPTFLAGS automatically
#
# The CCVER variable controls which GCC-version to use by default.  It
# should be set using ?= so as not to interfere with CCVER overrides from
# userland or the buildworld.  We currently recommend that an override NOT
# be set in /etc/make.conf and that gcc 3.4 not yet be used to build the boot
# blocks, boot loader, or the kernel.
#
#CCVER?=gcc34   # (use GCC 3.4, default)
#CCVER?=gcc40   # (use GCC 4.0, experimental, must define WANT_GCC40)
#
# Build gcc40 with world.  This won't make gcc40 the default compiler
#WANT_GCC40=yes
#
# CFLAGS controls the compiler settings used when compiling C code.
# Note that optimization settings above -O (-O2, ...) are not recommended
# or supported for compiling the world or the kernel - please revert any
# nonstandard optimization settings to -O before submitting bug reports
# to the developers.
#
#CFLAGS= -O -pipe
#
# CXXFLAGS controls the compiler settings used when compiling C++ code.
# Note that CXXFLAGS is initially set to the value of CFLAGS.  If you wish
# to add to CXXFLAGS value, += must be used rather than =.  Using =
# alone will remove the often needed contents of CFLAGS from CXXFLAGS.
#
# BDECFLAGS are a set of gcc warning settings that Bruce Evans has suggested
# for use in developing FreeBSD and testing changes.  They can be used by
# putting CFLAGS+=${BDECFLAGS} in /etc/make.conf.  -Wconversion is not
# included here due to compiler bugs, e.g., mkdir()'s mode_t argument.
#
BDECFLAGS=  -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \
   -Wcast-qual -Wchar-subscripts -Winline \
   -Wmissing-prototypes -Wnested-externs -Wpointer-arith \
   -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings
#
# WARNS_WERROR causes -Werror to be added when WARNS is in effect.
#WARNS_WERROR=  yes
#
# To compile just the kernel with special optimizations, you should use
# this instead of CFLAGS (which is not applicable to kernel builds anyway).
# There is very little to gain by using higher optimization levels, and doing
# so can cause problems.
#
#COPTFLAGS= -O -pipe
#
# Strip the file before installing.  Setting this to nothing will keep
# the debugging symbols in the installed files.
#STRIP= -s
#
# Compare before install
#INSTALL=install -C
#
# To build ppp with normal permissions
#PPP_NOSUID=true
# To enable installing ssh(1) with the setuid bit turned on
#ENABLE_SUID_SSH=   true
#
# To use bsdtar as the standard tar.  The default is GNU tar.
#WITH_BSDTAR=   true
#
# To avoid building various parts of the base system:
NO_BIND=true# do not build BIND
#NO_CRYPT=  true# do not build crypto code
#NO_CVS=true# do not build CVS
#NO_FORTRAN=true# do not build g77 and related libraries
NO_GAMES=   true# do not enter the games subdirectory
NO_I4B= true# do not build isdn4bsd package
#NO_IPFILTER=   true# do not build IP Filter package
#NO_LIBC_R= true# do not build libc_r (re-entrant version of libc)
NO_LPR= true# do not build lpr and related programs
#NO_MAILWRAPPER=true# do not build the mailwrapper(8) MTA selector
#NO_MODULES=true# do not build modules with the kernel
#NO_OBJC=   true# do not build Objective C support
#NO_OPENSSH=true# do not build OpenSSH
#NO_OPENSSL=true# do not build OpenSSL (implies NO_OPENSSH)
#NO_PKGTOOLS=   true# do not build included package tools (for pkgsrc)
NO_SENDMAIL=true# do not build sendmail and related programs
#NO_SHARE=  true# do not enter the share subdirectory
NO_X=   true# do not compile in XWindows support (e.g. doscmd)
#NOINFO=true# do not make or install info files

Re: buildworld error v1.8 - undefined reference to `EVP_sha256'

2007-02-01 Thread j s

On 2/1/07, YONETANI Tomokazu [EMAIL PROTECTED] wrote:

On Wed, Jan 31, 2007 at 03:10:21PM -0800, j s wrote:
 cc -O -pipe -mtune=pentiumpro
You have something similar to this

LDFLAGS=-L/usr/pkg/lib

in /etc/make.conf?  Try commenting out, or use a custom make.conf
only for {build,install}{kernel,world} to avoid this.  You can use
$__MAKE_CONF to switch make.conf files:


It appears that my custom LDFLAGS setting in the environment screwed
things up.  After replying to Sascha I got to thinking that might be
the case so I set about removing it from the environment an rerunning
the build.  Happy to report the build was successful.

 DragonFly 1.8.0-RELEASE #0: Thu Feb  1 08:54:00 PST 2007 


BTW, the LDFLAGS setting is in the root .cshrc file, not in the
make.conf file and nothing exists in the make.conf file to override
this setting.

Thanks,
js