Login
Username:

Password:

Remember me



Lost Password?

Register now!
Main Menu
Who's Online
1 user(s) are online (1 user(s) are browsing Forum)

Members: 0
Guests: 1

more...
   All Posts (nikolas)


(1) 2 »


Re: Does Contrib ABI v1 build at the moment?

Joined:
2017/9/11 14:28
From Basel
Group:
Member
Posts: 12
Offline
Quote:

Can you verify it has been created and exists under /root/linux-i386/bin/linux-i386/AROS/Developer/lib ?


As I wrote in the other post openssl was compiled but not copied in this location during "make contrib". I'll fix it.

Quote:

Also - you are building it under the root account? that's not a good idea, because if something misbehaves it can install files into places it shouldn't, over-writing your os's files (or worse deleting important things from your system).


You are right this is a very bad practice. Actually, I have a script that build an new vm with ubuntu, install the required packages, fetch and compile sources. I generally destroy the vm after every usage... I was too lazy to create and switch user :)

Posted on: 6/10 10:52
Transfer the post to other applications Transfer


Re: AmiSSL

Joined:
2017/9/11 14:28
From Basel
Group:
Member
Posts: 12
Offline
Hi Kalamatee,

I also see that it doesn't copy the library and include files during make install.
I'll give a look to it.

Posted on: 6/10 10:25
Transfer the post to other applications Transfer


Re: Does Contrib ABI v1 build at the moment?

Joined:
2017/9/11 14:28
From Basel
Group:
Member
Posts: 12
Offline

Posted on: 6/9 14:24
Transfer the post to other applications Transfer


Re: Does Contrib ABI v1 build at the moment?

Joined:
2017/9/11 14:28
From Basel
Group:
Member
Posts: 12
Offline
Hi Kalamatee

I downloaded last version from svn (55262) and tried to make a clean build. It stop here:

checking for winsock.h... (cached) no
checking for winsock2.h... (cached) no
checking for connect in libraries... cannot find connect
configure: error: cannot find connect function in libraries.
mmakefile:423: recipe for target '/root/linux-i386/bin/linux-i386/gen/contrib/development/libs/curl/curl/.configured' failed
make[1]: *** [/root/linux-i386/bin/linux-i386/gen/contrib/development/libs/curl/curl/.configured] Error 1
[MMAKE] make --no-print-directory TOP=/root/linux-i386 SRCDIR=/root/svn/AROS CURDIR=contrib/development/libs/curl TARGET=development-curl--configure --file=mmakefile development-curl--configure failed: 512
[MMAKE] Error: Error while running make in contrib/development/libs/curl: No such file or directory
Makefile:259: recipe for target 'contrib' failed
make: *** [contrib] Error 10

Is this the fix that should be done on configure script?
Do you have a workaround to continue the compilation?

Posted on: 6/9 12:50
Transfer the post to other applications Transfer


Re: AmiSSL

Joined:
2017/9/11 14:28
From Basel
Group:
Member
Posts: 12
Offline
Hi all,

I implemented the changes we discussed. They are on the previous link

Posted on: 6/9 7:32
Transfer the post to other applications Transfer


Re: AmiSSL

Joined:
2017/9/11 14:28
From Basel
Group:
Member
Posts: 12
Offline
Quote:

Kalamatee wrote:
Quote:

nikolas wrote:
> enabling -D__AROS__=1 -D__aros__=1
>shouldnt be neccessary

It looks that it is necessary, but I could use only one flag.


The cross compiler defines those (they are hard coded in it). If they weren't there, most things in the source tree would not compile correctly. if the code doesn't detect them, you are likely using the wrong compiler.


I checked better. The compiler inject __AROS__. My compilation failed because __aros__ is not injected. I modified it in the patch to be with capital case.


Quote:

Quote:

> --cross-compile-prefix=i386-aros
> sould be probably left to the system to determine (what > about the other targets)



I believe that should be determined/set by openssl's configure scripts.



I guess you are right. I wanted a shortcut to avoid to patch the Configure script of OpenSSL, but I understand the point here. I guess I can use $(AROS_TARGET_CPU) to find the prefix.

Quote:

Quote:

> ...
> -debug
> -should probably be left out to be specified in configure flag.

Do you how I can find them? Can someone suggest some mmakefile or documentation?


Configure injects some of those into the TARGET_CFLAGS, via the generated files from "config/". if you are building in the build system they will be automatically provided, unless you use something incorrectly.


I see. I'll modify that also.

Posted on: 6/8 15:55
Transfer the post to other applications Transfer


Re: Does Contrib ABI v1 build at the moment?

Joined:
2017/9/11 14:28
From Basel
Group:
Member
Posts: 12
Offline
Hi all,

I just wanted to report that when I try to build contrib I got this error:

Performing build in bin/linux-i386/gen/contrib/development/scm/git
LINK git-http-fetch
There are undefined symbols in 'git-http-fetch':
U zlibVersion
Makefile:2069: recipe for target 'git-http-fetch' failed
make[2]: *** [git-http-fetch] Error 1
mmakefile:377: recipe for target '/root/linux-i386/bin/linux-i386/gen/contrib/development/scm/git/.installed' failed

My environment should be clean. I tried to build hosted version with the last version from git repository.
Anyone is working on that?


Posted on: 6/8 13:36

Edited by nikolas on 2018/6/8 14:02:36
Edited by nikolas on 2018/6/8 14:03:20
Transfer the post to other applications Transfer


Re: AmiSSL

Joined:
2017/9/11 14:28
From Basel
Group:
Member
Posts: 12
Offline
> enabling -D__AROS__=1 -D__aros__=1
>shouldnt be neccessary

It looks that it is necessary, but I could use only one flag.

> no-threads
> -not sure. ptreads migt be used dunno, but it may need c++ static lib as a prerequisite.

I removed this one and I was able to compile as well. Now it should be thread-safe :)

> --cross-compile-prefix=i386-aros
> sould be probably left to the system to determine (what > about the other targets)
> ...
> -debug
> -should probably be left out to be specified in configure flag.


Do you how I can find them? Can someone suggest some mmakefile or documentation?

Posted on: 6/8 13:17
Transfer the post to other applications Transfer


Re: AmiSSL

Joined:
2017/9/11 14:28
From Basel
Group:
Member
Posts: 12
Offline
Hi Kalamatee,
thanks for the quick answer.

Quote:

by Kalamatee wrote:

would be if the final file in the patch (util/shlib_wrap.sh) is necessary?



No, it was just missing from my exclude list. I'll remove it

I see that "make test" from openssl was invoking a perl script to run the automated tests, and I cannot do the same in AROS. I guess the only way here is to reimplement it using AROS shell scripting or something similar. Any better idea?

I tried with sh but I see the posix implementation is still not completed.This the error I got while trying to execute the script:

The function posixc/sigprocmask() is not implemented.
[KRN] Trap signal 11, SysBase b8b991e0, KernelBase b8b99f44
SP=b9717370 FP=b9717388 PC=b96e347a
R0=0000000a R1=b9717f60 R2=0000000a R3=b971d948
R4=b97197d2 R5=ce7aaaa2

Posted on: 6/7 15:50
Transfer the post to other applications Transfer


Re: AmiSSL

Joined:
2017/9/11 14:28
From Basel
Group:
Member
Posts: 12
Offline
Hi all,

Finally I was able to compile all the tests and to make a proper mmakefile and patch.

You can find the two files on this link.
My notes during developments are here

I have successfully run some of the test on AROS, but I still have to compile make on my AROS ABI_V1 to be able to automatically run all of them.

Please give a look on it, since I do not have specific experience programming on Amiga or AROS, but I did my best reading some documentation and what was done for 1.0.1 version.

Posted on: 6/7 12:43

Edited by nikolas on 2018/6/7 13:46:19
Transfer the post to other applications Transfer



 Top
(1) 2 »




Search
Top Posters
1 paolone
paolone
4433
2 magorium
magorium
4095
3 nikolaos
nikolaos
4018
4 phoenixkonsole
phoenixkonsole
3928
5 deadwood
deadwood
2917
6 ncafferkey
ncafferkey
2796
7 mazze
mazze
2221
8 clusteruk
clusteruk
2112
9 damocles
damocles
1789
10 BSzili
BSzili
1513
© 2004-2018 AROS Exec