On Sun, 15 Apr 2007, [EMAIL PROTECTED] wrote:
> At 12:10 15/04/07 -0400, Woodchuck wrote:
>
> >The required symbols are in /usr/include/openssl/obj_mac.h
> >That file should have been included in rsa_x931.c implicitly,
> >when rsa_x931.c included /usr/include/openssl/objects.h
> >
> >I believe your copy of rsa_x931.c must be corrupt.
> >
> >This is from my source archive (OPENBSD_4) i.e. "stable":
> >[EMAIL PROTECTED] lib 0:18]# sha1 libssl/src/crypto/rsa/rsa_x931.c
> >SHA1 (libssl/src/crypto/rsa/rsa_x931.c) =
> >33a25cba2f3e0413bb2581d1ef89bb22cd7a2771
> >[EMAIL PROTECTED] lib 0:19]# wc libssl/src/crypto/rsa/rsa_x931.c
> > 177 677 4665 libssl/src/crypto/rsa/rsa_x931.c
>
> Mine too. What I do is download src.tar.gz and sys.tar.gz and untar
> them in /usr/src.
> I am. But apparently this isn't the problem. After the update:
>
> $ ls -l rsa_x*
> -rw-r--r-- 1 root wheel 4665 Jun 27 2006 rsa_x931.bogus.c
> -rw-r--r-- 1 root wheel 4665 Apr 15 17:28 rsa_x931.c
>
> $ diff rsa_x931.bogus.c rsa_x931.c
Agree.
spamd gave me some more time to think about it, and I couldn't
imagine how this could have failed.
> I think I must have done something to the machine itself, added some
> file or symlink somewhere, that makes it different from my test box (I
> updated both machines exactly the same way following the Update FAQ),
> because yesterday I successfully compiled swish-e on my test box, but
> when I tried to compile it today on the real box it too failed. (I've
> appended the end of its output to this message.)
This theory is sounding good.
> If you were in my shoes where would you start looking for the
> difference between the two machines? My idea is to make a list of
> every file on each machine that *isn't* in the distribution, eliminate
> those that are the same, and see what I'm left with.
heh. I've been in this jam myself, but not recently.
I start with "find /usr/src | sort" on each machine and
then diff the two output files.
But maybe your problem isn't in /usr/src anymore, but since you've
been updating, something bad got put elsewhere, such as /usr/include/.
>From your previous output, some include file or files are
missing or broken, or Makefiles are broken or stuff under /usr/share/mk
is broken, or /etc/mk.conf has something bogus in it.
What I would do in your place is to rm -r /usr/src /usr/obj
and re-expand the source tar into /usr/src.
Then I would update using cvs, rather than patch. I would update
to the OPENBSD_4 tag, giving me a "4.0-stable" source tree.
Then I would "make build" in /usr/src and recompile the whole system.
> Here's how the swish-e compilation failed:
This swish-e is neither port nor core, so it's a little harder
for me to debug.
I don't think the problem is necessarily in swish.
> /usr/bin/ld: warning: libz.so.3.0, needed by
> /usr/local/lib/libswish-e.so.2.0, may conflict with libz.so.4.1
> /usr/bin/ld: warning: libm.so.1.0, needed by
> /usr/local/lib/libswish-e.so.2.0, may conflict with libm.so.2.3
Those ^^^^ are not really problems, but the configuration of
swish-e may be old or faulty. It looks like it is including
routines in its own library that are also in libz and libm, and
then also referencing those libraries. This is not uncommon
to see in "portable" code.
I'm dloading the code and will try to compile it myself. I'll be
in touch off-list to see whether we have the same versions of
the source, etc etc.
> swish.o(.text+0x1ac3): In function `write_index_file':
> /usr/local/src/swish-e-2.4.5/src/swish.c:1689: undefined reference to
> `comma_long'
These and the other undefined references talk about something
wrong with swish and its configuration for BSD.
Just offhand, are you using "gmake" to make swish-e? It has Linux
origins; many Linux developers are unaware that there is any
other flavor of make, and that our make is actually quite different
from theirs. (They call our make "pmake", by the way, sometimes
they have to use it when compiling BSD origin stuff.)
Dave
--
Resistance is futile. You've already been assimilated.
_______________________________________________
Openbsd-newbies mailing list
[email protected]
http://mailman.theapt.org/listinfo/openbsd-newbies
