Browsing this Thread:
1 Anonymous Users
|
Re: Does Contrib ABI v1 build at the moment?
|
||||
|---|---|---|---|---|
|
Quite a regular
![]() |
I haven?t used SVN in many years, and it may not have anything to do with it but is it possible to get a status flag somewhere that says if a current tree is failing or passing its build at the present time?
For example, right now it sounds like a current checkout and build would be expected to fail. With git all of this would be done on a feature branch and only merged into master when it is known that it builds (unexpected issues aside of course). Just curious ????
Posted on: 2018/6/10 18:57
|
|||
|
||||
|
Re: Does Contrib ABI v1 build at the moment?
|
||||
|---|---|---|---|---|
|
Home away from home
![]()
|
Quote:
I?ve already fixed and tested this in trunk. The only remaining issue is to fix curl again since it fails to detect ssl during configure, resulting to it being compiled without ssl support again and therefore breaking in the git build.
Posted on: 2018/6/10 18:01
|
|||
|
||||
|
Re: Does Contrib ABI v1 build at the moment?
|
||||
|---|---|---|---|---|
|
Not too shy to talk
![]() |
Quote:
As I wrote in the other post openssl was compiled but not copied in this location during "make contrib". I'll fix it. Quote:
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: 2018/6/10 17:52
|
|||
|
||||
|
Re: Does Contrib ABI v1 build at the moment?
|
||||
|---|---|---|---|---|
|
Home away from home
![]()
|
Quote:
Ok .. ive removed the link with ssl for the connect test
Posted on: 2018/6/10 0:42
|
|||
|
||||
|
Re: Does Contrib ABI v1 build at the moment?
|
||||
|---|---|---|---|---|
|
Home away from home
![]()
|
Quote:
well, according to that openssl hasn't been built /root/linux-i386/bin/linux-x86_64/tools/crosstools/i386-aros-ld: cannot find -lssl (*) Can you verify it has been created and exists under /root/linux-i386/bin/linux-i386/AROS/Developer/lib ? 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). Edit: *- having said that, libssl shouldnt be necessary at this point - I will see about making it try the compile without it specified (though that will just hide the fact ssl isnt found, and curl will be built without ssl support again for you).
Posted on: 2018/6/9 21:43
Edited by Kalamatee on 2018/6/9 22:11:24
Edited by Kalamatee on 2018/6/9 22:18:33 Edited by Kalamatee on 2018/6/9 22:21:21 |
|||
|
||||
|
Re: Does Contrib ABI v1 build at the moment?
|
||||
|---|---|---|---|---|
|
Not too shy to talk
![]() |
Here the loghttps://pastebin.com/yxW1NAe7
Posted on: 2018/6/9 21:24
|
|||
|
||||
|
Re: Does Contrib ABI v1 build at the moment?
|
||||
|---|---|---|---|---|
|
Home away from home
![]()
|
Quote:
That should be working in the patch .. can you post the config.log somewhere (like pastebin), so that I can see why it fails? It should be in bin/linux-i386/gen/contrib/development/libs/curl/curl/ I?ve done a few clean builds with it now and they all build correctly. The fix needed in configure is to stop it listing -lssl twice in the CURL_LIBS - otherwise it causes undefined symbols in the binary for some reason. Currently I get the mmakefile to just replace them using sed, but that?s later in the process than your failure. Quote:
No but if you can get me the log I will see if I can find out what?s wrong and fix it.
Posted on: 2018/6/9 20:27
|
|||
|
||||
|
Re: Does Contrib ABI v1 build at the moment?
|
||||
|---|---|---|---|---|
|
Not too shy to talk
![]() |
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: 2018/6/9 19:50
|
|||
|
||||
|
Re: Does Contrib ABI v1 build at the moment?
|
||||
|---|---|---|---|---|
|
Home away from home
![]()
|
Just a few warnings/thing ive noticed:
# the binaries for git/curl/etc are quite massive due to linkling in curl/openssl rather than them being shared libraries. # curl prompts for the "home" directory, so probably wants to be run in the (unix) abcshell - make sure and call 'sh' before using them or launch the shell directly using the shortcut under developer. it will work if you close the home requestors but its a bit of an annoyance otherwise. # git still isn't working yet (crashes here), and curl crashed after downloading a 100MB test file, but that was likely due to the limited memory in the m68k setup I tested with. it was also quite slow under winuae/uaenet.device - only reaching about 90k/s # curl outputs the download info on a new line every time if the shell isn't wide enough to show a complete line of output on one line. # they probably need a good bit of stack. I used the commands on this page to test curl -:https://support.symantec.com/en_US/article.TECH247472.html Edit: Another quick test of curl .. ![]()
Posted on: 2018/6/9 17:21
Edited by Kalamatee on 2018/6/9 17:43:20
Edited by Kalamatee on 2018/6/9 17:44:24 |
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.









