I am trying to build the 1.1.1p and 3.0.4 versions of OpenSSL. Each
version now fails in the same place (test/v3ext.c). The error is about
undefined ASIdentifiers, etc. in the newly added test_asid() function.
It looks like the newly added test_asid() function needs an '#ifndef
OPENSSL_NO_RF
h,22th,25th Apr
Holiday – 15th Apr
-Original Message-
From: Tomas Mraz
Sent: 21 April 2022 11:24 PM
To: Gaurav Mittal11 ; Michael Wojcik
; openssl-users@openssl.org
Subject: [EXTERNAL] Re: Openssl 3.0.2- Build error - catgets_failed
Maybe https://github.com/openssl/openssl/pull/18136 co
aving directory '/home/infod3/tools/openssl-3.0.2'
> gmake: *** [Makefile:1680: build_sw] Error 2
>
> --
> Gaurav Mittal
>
> -Original Message-
> From: openssl-users On Behalf Of
> Michael Wojcik
> Sent: 21 April 2022 09:57 PM
> To: openssl-users@openssl.org
&
enssl-3.0.2'
gmake: *** [Makefile:1680: build_sw] Error 2
--
Gaurav Mittal
-Original Message-
From: openssl-users On Behalf Of Michael
Wojcik
Sent: 21 April 2022 09:57 PM
To: openssl-users@openssl.org
Subject: [EXTERNAL] RE: Openssl 3.0.2- Build error - catgets_failed
> From: Gau
> From: Gaurav Mittal11
> Sent: Thursday, 21 April, 2022 09:55
>
> Yes, I have gone through internet search, I have not found any clue.
>
> Still same error even after setting LANG to C
>
> Yes, HP is kind of legacy server and very less help available on internet.
>
> Any more suggestions woul
ed
hpux64-ia64-cc
make
--
Gaurav Mittal
-Original Message-
From: openssl-users On Behalf Of Michael
Wojcik
Sent: 20 April 2022 06:56 PM
To: openssl-users@openssl.org
Subject: [EXTERNAL] RE: Openssl 3.0.2- Build error - catgets_failed
> From: openssl-users On Behalf Of Gaurav
>
> From: openssl-users On Behalf Of Gaurav
> Mittal11
> Sent: Wednesday, 20 April, 2022 06:52
> ...
> as: "crypto/aes/aes-ia64.s", catgets_failed 2: catgets_failed 1052:
> catgets_failed - IDENT
A web search isn't turning anything up, but you probably tried that already.
I wonder if "catgets_f
Hi,
I am using HP-UX B.11.31 U server.
While compiling openssl 3.0.2, I am getting below error along with warnings,
any help would be appreciated.
Warning 67: "include/openssl/txt_db.h", line 12 # Invalid pragma name: 'once'
(ignored).
# pragma once
Warning 67: "includ
Hi David, Viktor and all other people,
Thanks very much for all your detailed explanation and time!
Best Regards
Nan Xiao
On Sun, Apr 4, 2021 at 3:21 AM David von Oheimb wrote:
>
> Hi Nan, Viktor, et al.,
>
> From: openssl-users On Behalf Of
> Viktor Dukhovni Sent: Wednesday, 31 March, 2021 1
Hi Nan, Viktor, et al.,
/From: openssl-users https://mta.openssl.org/mailman/listinfo/openssl-users>> On Behalf Of
Viktor//Dukhovni //Sent: Wednesday, 31 March, 2021 10:31/
> Most likely you haven't configured a suitable CAfile and/or CApath,
> which contains the root CA that ultimately issued Goo
Hi,
I am getting the below build error with latest openssl 1.1.1g version. Can
someone please help to resolve this issue?
ERROR: Failure expanding variable None, expression was libcrypto libssl
openssl-conf openssl-engines openssl-misc
${@bb.utils.contains('PTEST_ENABLED', '1&#
Hello,
I am working for a project which has dependency on openssl library. When I
try to build the openssl package with below bit bake recipe (got from open
embedded yocto ) it is failing with below errors.Could you please help to
resolve my issue.
http://cgit.openembedded.org/openembedded-core/t
You might want to show the whole command line that caused this error,
and it would help if we could have a look at the libcrypto.map you
got.
To be more effective, it might be a good idea to create an issue for
this on github: https://github.com/openssl/openssl/issues/new/choose
Cheers,
Richard
Hi,
Trying to build openssl-1.1.1b on solaris sparc 32 bit machine.
Getting some error with respect to "file format not recognized"
-lsocket -lnsl -ldl -pthread
/v/toolchain/SunOS-5.10-sparc/binutils-2.30/bin/gld:libcrypto.map: file
format not recognized; treating as linker script
/v/
Hello,
I’ve been given a CentOS VM and started by installing OpenSSL 1.02q.
wget https://www.openssl.org/source/openssl-1.0.2q.tar.gz
tar -xvf openssl-1.0.2q.tar.gz
cd openssl-1.0.2q
./config --prefix=/usr/local/openssl
make depend
make
make test
During the “make test” I get:
make[2]: Entering d
Added "/safeseh" in assembler flags and problem got solved. Thank you very
much.
--
Sent from: http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
SAFESEH requires any code that sets up Win32/i386 SEH handlers
to include special assembler directives to add the handler code
address to a special list which the linker then puts in the
compiled program for the Windows runtime (NTDLL.DLL etc.) to
check to make sure it is only calling back to your
Thanks for reply Michael.
I am sure i gave 32-bit build only. "BuildWinLibs.bat vs2015 x32d clean"
This is the comment i gave for build. Here "x32r" means 32-bit release
build.
Here is the error code(text).
rc /fo"tmp32dll/MSVC14.0\libeay32.res" /d CRYPTO ms\version32.rc
Microsoft (R)
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of sakdev
> Sent: Thursday, October 18, 2018 06:09
>
> To resolve this we added /SAFESEH flag in linker flags, and started build.
> But build got failed with "Unable to generate SAFESEH image" error.
You appear to have ad
Hi,
We are using openssl-1.0.2j. For security compliance we scanned libeay32.dll
with binscope binary analyzer. Binscope result is showing *“SafeSEHCheck
(FAIL)”*.
To resolve this we added /SAFESEH flag in linker flags, and started build.
But build got failed with "Unable to generate SAFESEH ima
SSL version-specific? SSL 1.1.0 builds clean on the same machine
I'm wondering if the solution is code changes or
On 3/1/18 04:27, Andy Polyakov wrote:
I mean it might happen that it's not version-specific...
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/l
On 03/01/18 01:46, Norm Green wrote:
> It looks like 32 bit builds set the -WX flag (treat warnings as errors)
> while the 64 bit builds don't.
>
>
> cl -W3 -wd4090 -Gs0 -GF -Gy -nologo /MDd /Od -WX /Zi
> /Fdossl_static /I "." /I "crypto\include" /I "include" /I
> "crypto\ec\curve448\arc
It looks like 32 bit builds set the -WX flag (treat warnings as errors)
while the 64 bit builds don't.
cl -W3 -wd4090 -Gs0 -GF -Gy -nologo /MDd /Od -WX /Zi
/Fdossl_static /I "." /I "crypto\include" /I "include" /I
"crypto\ec\curve448\arch_32" /I "crypto\ec\curve448" -DDSO_WIN32
-DOP
Hello.
Not sure if this is a Bug or not:
Steps:
1.) perl Configure no-ssl3 no-tls1 no-idea no-mdc2 no-rc5 VC-WIN32
--prefix=C:\opensslx86
2.) ms\do_nasm.bat or ms\do_ms.bat
3.) Message Output with ms\do_ms.bat usage:
perl util\mkfiles.pl 1>MINFO
perl util\mk1mf.pl no-asm VC-WIN32 1>ms\nt.mak
Hello,
Getting following error when trying to build openssl-1.0.1e for Win CE
Compiling using visual studio 2005 command prompt.
cl.exe /Fotmp32dll_X86\b_sock.obj -Iinc32 -Itmp32dll_X86 /MC /O1i /W3 /
WX /GF /Gy /nologo -DUNICODE -D_UNICODE -DOPENSSL_SYSNAME_WINCE -DWIN32_LEAN_AND
_MEAN
On Tue, May 21, 2013 at 11:00 AM, Viktor Dukhovni
wrote:
> If so, this is a Windows Perl bug IMHO. The parent should wait
> for the child to exit with close(STDOUT) in either scenario.
> Any special treatment of STDOUT should be reset after
>
> open STDOUT,"|cmd";
>
> in such a way as to
On Tue, May 21, 2013 at 10:14:27AM -0600, Phillip Hellewell wrote:
> Good news, I found the bug! I got thinking, why is x86_64-gf2m the
> only one giving me a problem? So I compared x86_64-gf2m.pl to the
> others and found that it has this line:
> open STDOUT,"| \"$^X\" $xlate $flavour $outp
Good news, I found the bug! I got thinking, why is x86_64-gf2m the
only one giving me a problem? So I compared x86_64-gf2m.pl to the
others and found that it has this line:
open STDOUT,"| \"$^X\" $xlate $flavour $output";
whereas the others have this:
open OUT,"| \"$^X\" $xlate $flavour $
I forgot to mention, I am using perl.exe version 5.16.3 and nasm.exe
version 2.10.07.
Phillip
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@ope
On Tue, May 21, 2013 at 9:08 AM, Phillip Hellewell wrote:
> But when executed from my build script (a batch file), it runs into
> problems.
Here is a copy of my build script. Can anyone spot a problem with it?
@echo off
if "%1"=="" goto buildall
setlocal
cd /d "%~dp0.."
@call target\dependency
On Tue, May 21, 2013 at 5:33 AM, Dr. Stephen Henson wrote:
> Just tried it myself with Visual Studio 2012, nasm version 2.10.07 and it
> compiles with no problems for me. I also tried it without nasm (i.e. ml64) and
> that worked OK too.
Ok, this is very helpful to know that it is working for oth
On Mon, May 20, 2013, Phillip Hellewell wrote:
> On Mon, May 20, 2013 at 1:12 PM, Phillip Hellewell wrote:
> > Should I try to patch it myself?
>
> FYI, the linker error is occurring because nasm is failing with a ton
> of errors on x86_64-g2m.asm, I think maybe because it is creating the
> wron
On 5/21/2013 2:04 AM, Phillip Hellewell wrote:
On Mon, May 20, 2013 at 1:12 PM, Phillip Hellewell wrote:
Should I try to patch it myself?
FYI, the linker error is occurring because nasm is failing with a ton
of errors on x86_64-g2m.asm, I think maybe because it is creating the
wrong type of a
It might be better if you specify how you set up your environment, what
versions of perl and nasm you used, and what sequence of commands you used.
I usually do a cut-down static build in an environment based on the Windows
Driver Kit, and I've built 1.0.1e using nasm without problems. I just tr
On Mon, May 20, 2013 at 1:12 PM, Phillip Hellewell wrote:
> Should I try to patch it myself?
FYI, the linker error is occurring because nasm is failing with a ton
of errors on x86_64-g2m.asm, I think maybe because it is creating the
wrong type of asm.
So I tried masm instead, and it is working s
On Thu, May 16, 2013 at 5:27 PM, Phillip Hellewell wrote:
> But do I have to sacrifice performance to be able to upgrade to 1.0.1?
Anyone? Can I be the only one in the whole world who wants to build
openssl on Windows 64-bit with optimized assembly routines?
Should I try to patch it myself? Sh
I'm trying to upgrade from 0.9.8y to 1.0.1e, but I'm getting this linker error.
link /nologo /subsystem:console /opt:ref /debug /dll
/out:out32dll\libeay32.dll /def:ms/LIBEAY32.def
@C:\Users\PHELLE~1\AppData\Local\Temp\nm6C7E.tmp
Creating library out32dll\libeay32.lib and object out32dll\libea
Hi,
I am getting error while linking with 1.0.1c build for 64 bit platform. Here
is what I did,
1. I build openssl as,
./Configure linux-generic64 --shared
make build_libs
2. Then I tried to link my application with the library and it gives
the following error,
openssl/libcr
own)bug?
Greetings
Markus
Original-Nachricht
> Datum: Thu, 22 Jul 2010 13:56:25 +0200
> Von: "Markus Hofer"
> An: openssl-users@openssl.org
> Betreff: openssl build error for embedded systems
> Hi
>
> I am currently working on building openssl for an embedde
Hi
I am currently working on building openssl for an embedded system. Since the
only things I need on the embedded system are SHA, MD5 and HMAC(in order to
fit net-snmp later on) I’m trying to cut down openssl as much as possible.
I am using openssl 0.9.8o
So I am doing the following things
Hi
I am currently working on building openssl for an embedded system. Since the
only things I need on the embedded system are SHA, MD5 and HMAC(in order to
fit net-snmp later on) I’m trying to cut down openssl as much as possible.
I am using openssl 0.9.8o
So I am doing the following things
On 17-06-2010 23:40, Harshvir Sidhu wrote:
Hey,
I was trying to build the openssl library with the Visual Studio
2005 configurations for CE.
I am getting bunch of errors, first it gave error for standart C
string functions. I defined the macro _CRT_SECURE_NO_WARNINGS and it
worked for that
Yeah i am doing the tweaking to go through errors, but my assumption was
that its a released code, so it should build without any error.
so i could be doing something wrong in terms of setting up environment, but
i am following the steps from Install.wce file.
On Thu, Jun 17, 2010 at 6:04 PM, Ger
Without having checked, so caveat emptor:
0)
answer final question: MSVC200x should do okay, generically speaking.
1)
The @90 error reads as if a (IMO hacky) local LoadLibraryA prototype line
mismatches with the official one; remove the one at 90 in the openssl source
file dso_win32.c, I'd say.
Hey,
I was trying to build the openssl library with the Visual Studio 2005
configurations for CE.
I am getting bunch of errors, first it gave error for standart C string
functions. I defined the macro _CRT_SECURE_NO_WARNINGS and it worked for
that.
Then i needed to define macro OPENSSL_SYSNAME_
@openssl.org
Subject: RE: fips build error on HP PA32
Hi David,
Thanks for the help. I already have a HP system, but getting the error
mentioned below when building a .sl.
Regards,
--Vikram
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org
, February 11, 2010 2:41 PM
To: openssl-users@openssl.org
Subject: Re: fips build error on HP PA32
Vikram Arwade wrote:
> Hi All,
>
>
>
> I am running into a build(fips) break on HP 11.11 PA32. Here is the
error:
>
>
>
>
>
> + + /fips_premain_dso ./libtem
Vikram Arwade wrote:
Hi All,
I am running into a build(fips) break on HP 11.11 PA32. Here is the error:
+ + /fips_premain_dso ./libtemp.sl
3814:error:2506A067:DSO support routines:DL_LOAD:could not load the
shared library:dso_dl.c:135:filename(./libtemp.sl): Exec format error
381
Hi All,
I am running into a build(fips) break on HP 11.11 PA32. Here is the
error:
+ + /fips_premain_dso ./libtemp.sl
3814:error:2506A067:DSO support routines:DL_LOAD:could not load the
shared library:dso_dl.c:135:filename(./libtemp.sl): Exec format error
3814:error:25070067:DSO suppor
Hi All,
I'm trying to get ssl support for my server running SLES 10 and python
2.4.5 and I'd like to send emails automatically. I just installed
openssl 0.9.8i with no problems. It installed to the usual
/usr/local/ssl. I then ran python setup.py build_ext
-I/usr/local/ssl/include -L/usr/local/
Folks,
I just got the 0.9.9dev SNAPSHOT (openssl-SNAP-20081227.tar.gz) and
for a WIN32 build, I got the build error:
perl crypto\camellia\asm\cmll-x86.pl win32n /MDd /Od -DDEBUG
-D_DEBUG -DOPENSSL_THREADS -DDSO_W
IN32 -W3 -WX -Gs0 -GF -Gy -nologo -DOPENSSL_SYSNAME_WIN32
That did it... Though the file was in /crypto/perlasm
Thanks a lot!
James
James Owen
-Original Message-
From: Thomas Jansen <[EMAIL PROTECTED]>
Date: Thu, 11 Sep 2008 13:21:02
To:
Subject: Re: build error vsc++express 2008 win32 openssl
James Owen wrote:
>
>
>
>
Duh. I see now you were showing your path... Thanks again.
James
--Original Message--
From: James Owen
To: openssl-users@openssl.org
ReplyTo: [EMAIL PROTECTED]
Subject: Re: build error vsc++express 2008 win32 openssl
Sent: Sep 11, 2008 09:56
That did it... Though the file was in
James Owen wrote:
now I get a new failure only with openssl-0.9.8h:
Assembling: .\crypto\sha\asm\s1_win32.asm
.\crypto\sha\asm\s1_win32.asm(13) : error A2008:syntax error : integer
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
9.0\VC\BIN
\ml.EXE"' : return code '0
I tried building the sources (openssl-0.9.7m, openssl-0.9.8g,
openssl-0.9.8h) with 2008 express and failed every time with the same
error.
cl /Fotmp32dll\cversion.obj -Iinc32 -Itmp32dll /MD /W3 /WX /
Ox /O2 /Ob2
/Gs0 /GF /Gy /nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN -
) : error A2008: : mm
NMAKE : fatal error U1077: 'ml' : return code '0x1'
Stop.
Please instruct actions to be taken for this build error.
In addition, the build of co_win32.asm succeeded.
Thanks!
Takurou Saitou
__
I'm trying to build 0.9.8g using cygwin.
"config" ran fine, looking at the output it shows
-
Operating system: i686-whatever-cygwin
Configuring for Cygwin
Configuring for Cygwin
no-camellia [default] OPENSSL_NO_CAMELLIA (skip dir)
no-gmp [default] OPENSS
bump than moving from a to b. Thanks.
,
Josh.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Marek Marcola
> Sent: Monday, May 15, 2006 11:13 AM
> To: openssl-users@openssl.org
> Subject: Re: OpenSSL 0.9.8b build error
>
>
Hello,
> I'm trying to build OpenSSL 0.9.8b on HP Itanium and I'm running into
> some problems during the make install step. I'm didn't notice any
> errors during configure or make and make test passed. I'm able to
> build 0.9.8a with the exact same steps. Has anyone else seen this?
> Any sugge
I'm trying to build
OpenSSL 0.9.8b on HP Itanium and I'm running into some problems during the make
install step. I'm didn't notice any errors during configure or make and
make test passed. I'm able to build 0.9.8a with the exact same
steps. Has anyone else seen this? Any suggestions on
gcc -I.. -I../.. -I../../include -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS
-D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m32 -mcpu=ultrasparc -O3
-fomit-frame-pointer -Wall -DB_ENDIAN -DBN_DIV2W -DMD5_ASM -c -c -o
des_enc-sparc.o des_enc-sparc.S
des_enc-sparc.S: Assembler messages:
des_enc-sparc.S:205
Title: Message
I'm trying to build
OpenSSL 0.9.8a on Solaris 8 and I'm running into problems. Any pointers
would be greatly appreciated.
Here is my build
process:
./config
--openssldir=/home/snow/jfenlason/solaris/lib/opensslSharedDist threads
sharedmake
Then I get the
following error
I am attempting to use rpmbuild to make an openssl binary from the latest
openssl release (openssl-0.9.7f) as of march 22, 2005. This seems to be my best
option since I have an older version of openssl that was installed with RH9 as
an RPM. The error I get is:
RPM build error: File not found
Hi,
I'm trying to build openssl out of the latest cvs on FreeBSD.
I got the following error:
(cd asm; /usr/bin/perl5 aes-586.pl a.out -I.. -I../.. -I../../include
-DOPENSSL_THREADS -pthread -D_THREAD_SAFE -D_REENTRANT -DDSO_DLFCN
-DHAVE_DLFCN_H -DL_ENDIAN
1)
./config -prefix=/usr/local/webservers/ossl -openssldir=/usr/local/webserve
rs/ossl shared threads
.
.
.
make[1]: Leaving directory `/usr/local/webservers/src/openssl-0.9.7c/test'
Configured for aix43-cc.
2)gmake
.
.
.
cc -o
rsa_test -I.. -I../include -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DL
On Mon, Jan 20, 2003, Jasper Spit wrote:
> Hi,
>
> I'm trying to build 0.9.7 with BC++ Builder 6, but it fails with the
> following error :
>
> bcc32 -otmp32\x_all.obj -Iinc32 -Itmp32 -DWIN32_LEAN_AND_MEAN -q
> -w-aus
> -w-par -w-inl -c -tWC -tWM -DOPENSSL_SYSNAME_WIN32 -DL_ENDIAN
> -DDS
Hi,
I'm trying to build 0.9.7 with BC++ Builder 6, but it fails with the
following error :
bcc32 -otmp32\x_all.obj -Iinc32 -Itmp32 -DWIN32_LEAN_AND_MEAN -q
-w-aus
-w-par -w-inl -c -tWC -tWM -DOPENSSL_SYSNAME_WIN32 -DL_ENDIAN
-DDSO_WIN32 -D_str
icmp=stricmp -O2 -ff -fp -DBN_ASM -DMD5_ASM -
Hi!
I took 0.9.7 from OpenSSL.org and tried compiling it on Windows NT4 sp6a
with Visual Studio command line tools. I followed the instructions of
install.w32 but got the following error with ms\do_nasm:
cl /Fotmp32dll\n_pkey.obj -Iinc32 -Itmp32dll /MD /W3 /WX /G5 /Ox
/O2 /Ob2 /Gs0 /GF
> Bill Shurtleff wrote:
>
> Hello,
>
> I'm building OpenSSL 0.9.5 under Windows NT using the MSASM 6.11 assembler.
> When I assemble the assembly I get the following message:
>
> ..\crypto\sha\asm\s1-win32.asm(1711): error A2006: undefined symbol :
> L001shortcut
>
> Is it legal to jump like t
> Bill Shurtleff wrote:
>
> Hello,
>
> I'm building OpenSSL 0.9.5 under Windows NT using the MSASM 6.11
> assembler. When I assemble the assembly I get the following message:
>
> ..\crypto\sha\asm\s1-win32.asm(1711): error A2006: undefined symbol :
> L001shortcut
>
> Is it legal to jump like t
Hello,
I'm building OpenSSL 0.9.5 under Windows NT using
the MSASM 6.11 assembler. When I assemble the assembly I get the following
message:
..\crypto\sha\asm\s1-win32.asm(1711): error A2006:
undefined symbol : L001shortcut
Is it legal to jump like that from one text segment
to another
71 matches
Mail list logo
