Xymon Mailing List Archive search

4.3.26 build fail

16 messages in this thread

list Matthew Daubenspeck · Fri, 18 Mar 2016 09:45:17 -0400 ·
I'm sure I'm missing something simple, but trying to compile 4.3.26
fails:

gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -DLINUX -I/home/xymon/xymon-4.3.26/include  -o
xymonnet -Wl,--rpath, xymonnet.o contest.o httptest.o httpresult.o
ldaptest.o dns.o dns2.o httpcookies.o -lcares  ../lib/libxymontime.a
../lib/libxymoncomm.a  -lssl -lcrypto   ../lib/libxymon.a -lpcre
contest.o: In function `setup_ssl':
/home/xymon/xymon-4.3.26/xymonnet/contest.c:486: undefined reference to
`SSLv3_client_method'
collect2: error: ld returned 1 exit status
Makefile:33: recipe for target 'xymonnet' failed
make[1]: *** [xymonnet] Error 1
make[1]: Leaving directory '/home/xymon/xymon-4.3.26/xymonnet'
build/Makefile.rules:102: recipe for target 'xymonnet-build' failed
make: *** [xymonnet-build] Error 2

Any suggestions?
list Paul Root · Fri, 18 Mar 2016 14:32:32 +0000 ·
Do you have openssl_devel installed?
quoted from Matthew Daubenspeck

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Matthew Daubenspeck
Sent: Friday, March 18, 2016 8:45 AM
To: xymon at xymon.com
Subject: [Xymon] 4.3.26 build fail

I'm sure I'm missing something simple, but trying to compile 4.3.26
fails:

gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -DLINUX -I/home/xymon/xymon-4.3.26/include  -o
xymonnet -Wl,--rpath, xymonnet.o contest.o httptest.o httpresult.o
ldaptest.o dns.o dns2.o httpcookies.o -lcares  ../lib/libxymontime.a
../lib/libxymoncomm.a  -lssl -lcrypto   ../lib/libxymon.a -lpcre
contest.o: In function `setup_ssl':
/home/xymon/xymon-4.3.26/xymonnet/contest.c:486: undefined reference to
`SSLv3_client_method'
collect2: error: ld returned 1 exit status
Makefile:33: recipe for target 'xymonnet' failed
make[1]: *** [xymonnet] Error 1
make[1]: Leaving directory '/home/xymon/xymon-4.3.26/xymonnet'
build/Makefile.rules:102: recipe for target 'xymonnet-build' failed
make: *** [xymonnet-build] Error 2

Any suggestions?

This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
list Matthew Daubenspeck · Fri, 18 Mar 2016 10:51:41 -0400 ·
quoted from Paul Root
On Fri, Mar 18, 2016 at 02:32:32PM +0000, Root, Paul T wrote:
Do you have openssl_devel installed?

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Matthew Daubenspeck
Sent: Friday, March 18, 2016 8:45 AM
To: xymon at xymon.com
Subject: [Xymon] 4.3.26 build fail

I'm sure I'm missing something simple, but trying to compile 4.3.26
fails:

gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -DLINUX -I/home/xymon/xymon-4.3.26/include  -o
xymonnet -Wl,--rpath, xymonnet.o contest.o httptest.o httpresult.o
ldaptest.o dns.o dns2.o httpcookies.o -lcares  ../lib/libxymontime.a
../lib/libxymoncomm.a  -lssl -lcrypto   ../lib/libxymon.a -lpcre
contest.o: In function `setup_ssl':
/home/xymon/xymon-4.3.26/xymonnet/contest.c:486: undefined reference to
`SSLv3_client_method'
collect2: error: ld returned 1 exit status
Makefile:33: recipe for target 'xymonnet' failed
make[1]: *** [xymonnet] Error 1
make[1]: Leaving directory '/home/xymon/xymon-4.3.26/xymonnet'
build/Makefile.rules:102: recipe for target 'xymonnet-build' failed
make: *** [xymonnet-build] Error 2
Yes, on Arch Linux, openssl is installed. It's worked perfectly with
many previous versions.
list Japheth Cleaver · Fri, 18 Mar 2016 10:40:00 -0700 ·
quoted from Matthew Daubenspeck
On Fri, March 18, 2016 7:51 am, Matthew Daubenspeck wrote:
On Fri, Mar 18, 2016 at 02:32:32PM +0000, Root, Paul T wrote:
Do you have openssl_devel installed?

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Matthew
Daubenspeck
Sent: Friday, March 18, 2016 8:45 AM
To: xymon at xymon.com
Subject: [Xymon] 4.3.26 build fail

I'm sure I'm missing something simple, but trying to compile 4.3.26
fails:

gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -DLINUX -I/home/xymon/xymon-4.3.26/include  -o
xymonnet -Wl,--rpath, xymonnet.o contest.o httptest.o httpresult.o
ldaptest.o dns.o dns2.o httpcookies.o -lcares  ../lib/libxymontime.a
../lib/libxymoncomm.a  -lssl -lcrypto   ../lib/libxymon.a -lpcre
contest.o: In function `setup_ssl':
/home/xymon/xymon-4.3.26/xymonnet/contest.c:486: undefined reference to
`SSLv3_client_method'
collect2: error: ld returned 1 exit status
Makefile:33: recipe for target 'xymonnet' failed
make[1]: *** [xymonnet] Error 1
make[1]: Leaving directory '/home/xymon/xymon-4.3.26/xymonnet'
build/Makefile.rules:102: recipe for target 'xymonnet-build' failed
make: *** [xymonnet-build] Error 2
Yes, on Arch Linux, openssl is installed. It's worked perfectly with
many previous versions.

Dumb question, but does 'openssl' include the development files as well
then on Arch? (Presumably, since it's worked before for you.)

Is it possible this is related to mitigation for DROWN or another openssl
issue taken within Arch to disable SSLv3? I seem to recall a recent set of
updates causing some unexpected ABI changes (functions disappearing
without any stub replacements) on several distributions.

Can you see if a previous known-working release tarball recompiles
successfully on this system?


Regards,
-jc
list Matthew Daubenspeck · Fri, 18 Mar 2016 13:51:49 -0400 ·
quoted from Japheth Cleaver
On Fri, Mar 18, 2016 at 10:40:00AM -0700, J.C. Cleaver wrote:
Dumb question, but does 'openssl' include the development files as well
then on Arch? (Presumably, since it's worked before for you.)
Yes it does. Package contents can be seen here if necessary:

https://www.archlinux.org/packages/core/x86_64/openssl/files/
quoted from Japheth Cleaver
Is it possible this is related to mitigation for DROWN or another openssl
issue taken within Arch to disable SSLv3? I seem to recall a recent set of
updates causing some unexpected ABI changes (functions disappearing
without any stub replacements) on several distributions.
I am assuming you are correct. They have a git commit commented with
"Let's try without SSLv3, too" on 2016-03-01.

http://tinyurl.com/zherj2c
quoted from Japheth Cleaver
Can you see if a previous known-working release tarball recompiles
successfully on this system?
Just tried the already installed version, 4.3.24, and it fails the exact
same way.
list Japheth Cleaver · Fri, 18 Mar 2016 11:32:34 -0700 ·
quoted from Matthew Daubenspeck
On Fri, March 18, 2016 10:51 am, Matthew Daubenspeck wrote:
On Fri, Mar 18, 2016 at 10:40:00AM -0700, J.C. Cleaver wrote:
Dumb question, but does 'openssl' include the development files as well
then on Arch? (Presumably, since it's worked before for you.)
Yes it does. Package contents can be seen here if necessary:

https://www.archlinux.org/packages/core/x86_64/openssl/files/
Is it possible this is related to mitigation for DROWN or another
openssl
issue taken within Arch to disable SSLv3? I seem to recall a recent set
of
updates causing some unexpected ABI changes (functions disappearing
without any stub replacements) on several distributions.
I am assuming you are correct. They have a git commit commented with
"Let's try without SSLv3, too" on 2016-03-01.

http://tinyurl.com/zherj2c
Can you see if a previous known-working release tarball recompiles
successfully on this system?
Just tried the already installed version, 4.3.24, and it fails the exact
same way.
Ahh, that would explain it then.

Can you see if this patch lets you build successfully?


-jc
list Matthew Daubenspeck · Fri, 18 Mar 2016 14:51:10 -0400 ·
quoted from Japheth Cleaver
On Fri, Mar 18, 2016 at 11:32:34AM -0700, J.C. Cleaver wrote:
Ahh, that would explain it then.

Can you see if this patch lets you build successfully?


-jc
patching file xymonnet/contest.c
patching file configure.server
patching file build/ssl.sh
patching file build/test-ssl3.c
patching file build/Makefile.test-ssl3
patch unexpectedly ends in middle of line
patch: **** malformed patch at line 114:

Did I patch it wrong?
list Japheth Cleaver · Fri, 18 Mar 2016 12:14:03 -0700 ·
quoted from Matthew Daubenspeck

On Fri, March 18, 2016 11:51 am, Matthew Daubenspeck wrote:
On Fri, Mar 18, 2016 at 11:32:34AM -0700, J.C. Cleaver wrote:
Ahh, that would explain it then.

Can you see if this patch lets you build successfully?


-jc
patching file xymonnet/contest.c
patching file configure.server
patching file build/ssl.sh
patching file build/test-ssl3.c
patching file build/Makefile.test-ssl3
patch unexpectedly ends in middle of line
patch: **** malformed patch at line 114:

Did I patch it wrong?
Hmm. It's possible something went odd encoding-wise, but as long as the
final lines of build/Makefile.test-ssl3 are:

clean:
       @rm -f test-ssl3.o test-ssl3

, then you should be fine. It's an svn diff and those last two are new files.


-jc
list John Thurston · Fri, 18 Mar 2016 11:28:40 -0800 ·
quoted from Matthew Daubenspeck
On 3/18/2016 10:51 AM, Matthew Daubenspeck wrote:
On Fri, Mar 18, 2016 at 11:32:34AM -0700, J.C. Cleaver wrote:
Ahh, that would explain it then.

Can you see if this patch lets you build successfully?


-jc
patching file xymonnet/contest.c
patching file configure.server
patching file build/ssl.sh
patching file build/test-ssl3.c
patching file build/Makefile.test-ssl3
patch unexpectedly ends in middle of line
patch: **** malformed patch at line 114:

Did I patch it wrong?
I suspect you have a truncated patch file.
The attached text is 115 lines long.


-- 
    Do things because you should, not just because you can.

John Thurston    XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Enterprise Technology Services
Department of Administration
State of Alaska
list Matthew Daubenspeck · Mon, 21 Mar 2016 09:40:39 -0400 ·
quoted from John Thurston
On Fri, Mar 18, 2016 at 11:28:40AM -0800, John Thurston wrote:
patching file xymonnet/contest.c
patching file configure.server
patching file build/ssl.sh
patching file build/test-ssl3.c
patching file build/Makefile.test-ssl3
patch unexpectedly ends in middle of line
patch: **** malformed patch at line 114:

Did I patch it wrong?
I suspect you have a truncated patch file.
The attached text is 115 lines long.
I must be doing something wrong then. I downloaded the patch directly
from the user list archives, and get the same error. Line 115 has
nothing but a + and a blank line. I tried the patch attachment via mutt,
and downloading it via here:

http://lists.xymon.com/archive/2016-March/043228.html
list Richard Hamilton · Mon, 21 Mar 2016 12:12:58 -0400 ·
The attachment.bin from that link is 115 lines, but does not have a newline
at the end of the 115th line.  There have been a lot of versions of "patch"
commands, and not all of them may be equally tolerant.

You could try getting a fresh copy of attachment.bin, and then modifying it
by adding the newline
echo >>attachment.bin

and then using that.

I don't recall having any problems, but I'm working on a Mac, which may
have a different version of "patch" than what you're using.

On Mon, Mar 21, 2016 at 9:40 AM, Matthew Daubenspeck <user-8598f5922460@xymon.invalid>
quoted from Matthew Daubenspeck
wrote:
On Fri, Mar 18, 2016 at 11:28:40AM -0800, John Thurston wrote:
patching file xymonnet/contest.c
patching file configure.server
patching file build/ssl.sh
patching file build/test-ssl3.c
patching file build/Makefile.test-ssl3
patch unexpectedly ends in middle of line
patch: **** malformed patch at line 114:

Did I patch it wrong?
I suspect you have a truncated patch file.
The attached text is 115 lines long.
I must be doing something wrong then. I downloaded the patch directly
from the user list archives, and get the same error. Line 115 has
nothing but a + and a blank line. I tried the patch attachment via mutt,
and downloading it via here:

http://lists.xymon.com/archive/2016-March/043228.html

list Richard Hamilton · Mon, 21 Mar 2016 12:16:15 -0400 ·
Oops, my server is on Solaris 11 , not on a Mac; I would have been using
GNU patch 2.7.5 probably.  But I might have gotten the patch a different
way (or even just copy/pasted it) when I got it.


On Mon, Mar 21, 2016 at 12:12 PM, Richard Hamilton <user-af55987f6d56@xymon.invalid>
quoted from Richard Hamilton
wrote:
The attachment.bin from that link is 115 lines, but does not have a
newline at the end of the 115th line.  There have been a lot of versions of
"patch" commands, and not all of them may be equally tolerant.

You could try getting a fresh copy of attachment.bin, and then modifying
it by adding the newline
echo >>attachment.bin

and then using that.

I don't recall having any problems, but I'm working on a Mac, which may
have a different version of "patch" than what you're using.

On Mon, Mar 21, 2016 at 9:40 AM, Matthew Daubenspeck <user-8598f5922460@xymon.invalid>
wrote:
On Fri, Mar 18, 2016 at 11:28:40AM -0800, John Thurston wrote:
patching file xymonnet/contest.c
patching file configure.server
patching file build/ssl.sh
patching file build/test-ssl3.c
patching file build/Makefile.test-ssl3
patch unexpectedly ends in middle of line
patch: **** malformed patch at line 114:

Did I patch it wrong?
I suspect you have a truncated patch file.
The attached text is 115 lines long.
I must be doing something wrong then. I downloaded the patch directly
from the user list archives, and get the same error. Line 115 has
nothing but a + and a blank line. I tried the patch attachment via mutt,
and downloading it via here:

http://lists.xymon.com/archive/2016-March/043228.html

list Matthew Daubenspeck · Mon, 21 Mar 2016 13:42:21 -0400 ·
quoted from Richard Hamilton
On Mon, Mar 21, 2016 at 12:12:58PM -0400, Richard Hamilton wrote:
   The attachment.bin from that link is 115 lines, but does not have a

   newline at the end of the 115th line.  There have been a lot of
quoted from Richard Hamilton
   versions of "patch" commands, and not all of them may be equally
   tolerant.
   You could try getting a fresh copy of attachment.bin, and then
   modifying it by adding the newline
   echo >>attachment.bin
   and then using that.
   I don't recall having any problems, but I'm working on a Mac, which may
   have a different version of "patch" than what you're using.
That worked, thanks a ton! Patched and compiled cleanly. Thanks for the
help!
list Japheth Cleaver · Mon, 21 Mar 2016 11:53:59 -0700 ·
quoted from Matthew Daubenspeck
On Mon, March 21, 2016 10:42 am, Matthew Daubenspeck wrote:
On Mon, Mar 21, 2016 at 12:12:58PM -0400, Richard Hamilton wrote:
   The attachment.bin from that link is 115 lines, but does not have a

   newline at the end of the 115th line.  There have been a lot of
quoted from Matthew Daubenspeck
   versions of "patch" commands, and not all of them may be equally
   tolerant.
   You could try getting a fresh copy of attachment.bin, and then
   modifying it by adding the newline
   echo >>attachment.bin
   and then using that.
   I don't recall having any problems, but I'm working on a Mac, which
may
   have a different version of "patch" than what you're using.
That worked, thanks a ton! Patched and compiled cleanly. Thanks for the
help!

Hi,

Just to confirm, there don't seem to be any issues at runtime either on
the SSLv3-less system?

-jc
list Matthew Daubenspeck · Tue, 22 Mar 2016 10:15:26 -0400 ·
quoted from Japheth Cleaver
On Mon, Mar 21, 2016 at 11:53:59AM -0700, J.C. Cleaver wrote:
Hi,

Just to confirm, there don't seem to be any issues at runtime either on
the SSLv3-less system?

-jc
Correct. Compiled, installed, and is running fine on my devel server.
list Japheth Cleaver · Tue, 22 Mar 2016 17:35:08 -0700 ·
quoted from Matthew Daubenspeck

On Tue, March 22, 2016 7:15 am, Matthew Daubenspeck wrote:
On Mon, Mar 21, 2016 at 11:53:59AM -0700, J.C. Cleaver wrote:
Hi,

Just to confirm, there don't seem to be any issues at runtime either on
the SSLv3-less system?

-jc
Correct. Compiled, installed, and is running fine on my devel server.
Perfect! Thanks for the confirmation.

-jc