Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
58 user(s) are online (34 user(s) are browsing Forums)

Members: 0
Guests: 58

more...

Support us!

Headlines

 
  Register To Post  

« 1 ... 4 5 6 (7) 8 9 10 ... 72 »
Re: Odyssey 1.23 progress
Just popping in
Just popping in


See User information
@kas1e

Well, did you change all the functions as i wrote above?

I remember icu had fun replacing : with /, which is why i had to disable that silly code.

Quote:

And finally, in udata.cpp, around line 1137, you might want to disable that code:
if (U_FILE_SEP_CHAR != U_FILE_ALT_SEP_CHAR) /* Windows: try "foo\bar" and "foo/bar" */
{
/* remap from alternate path char to the main one */
CharString altSepPath;
...
}

Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@Fab

Yep, i do it like this:

....

      
isICUData TRUE;
    }

/*    
#if (U_FILE_SEP_CHAR != U_FILE_ALT_SEP_CHAR)  // Windows:  try "foo\bar" and "foo/bar" 
    // remap from alternate path char to the main one 
    CharString altSepPath;
    if(path) {
        if(uprv_strchr(path,U_FILE_ALT_SEP_CHAR) != NULL) {
            altSepPath.append(path, *pErrorCode);
            char *p;
            while((p=uprv_strchr(altSepPath.data(), U_FILE_ALT_SEP_CHAR))) {
                *p = U_FILE_SEP_CHAR;
            }
#if defined (UDATA_DEBUG)
            fprintf(stderr, "Changed path from [%s] to [%s]\n", path, altSepPath.s);
#endif
            path = altSepPath.data();
        }
    }
#endif
*/

    
CharString tocEntryName/* entry name in tree format. ex:  'icudt28b/coll/ar.res' */
    
CharString tocEntryPath/* entry name in path format. ex:  'icudt28b\\coll\\ar.res' */

....


Maybe something else should be commented ? I can of course go usual brutal way, just return what i need to return at end of whole doOpenChoice() function (like those pkgName.data(), dataPath , etc), but that can make side-effect somewhere, and i do no want introduce new bugs by my crapo-hacks


Edited by kas1e on 2014/2/5 12:25:33
Edited by kas1e on 2014/2/5 12:26:26
Edited by kas1e on 2014/2/5 12:27:23
Go to top
Re: Odyssey 1.23 progress
Just can't stay away
Just can't stay away


See User information
@kas1e

Thanks for the detailed info on cross-compiling libICU.

As for your porting progress, I'm sure the path issue is something you can track down without resorting to any nasty workarounds. It's gotta be modifying the path somewhere!

Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@Fab
Fixing it by adding to the udata.cpp in the UDataPathIterator::UDataPathIterator function:

UDataPathIterator::UDataPathIterator(const char *inPath, const char *pkg,
                                     const 
char *item, const char *inSuffixUBool doCheckLastFour,
                                     
UErrorCode *pErrorCode)
{
#ifdef UDATA_DEBUG
        
fprintf(stderr"SUFFIX1=%s PATH=%s\n"inSuffixinPath);
#endif
    /** Path **/
    #ifndef __amigaos4__
    
if(inPath == NULL) {
        
path u_getDataDirectory();
    } else {
        
path inPath;
    }
    
#else
        
path "PROGDIR:Resource";        
    
#endif

    /** Package **/
    
if(pkg != NULL) {



Then it works, PROGDIR:Resource everywhere, and odyssey didn't crashes !

What is strange, is that path = u_getDataDirectory();, return PROGDIR/Resource, and not PROGDIR:Resource. I.e. if at begining of UDataPathIterator::UDataPathIterator i add:

Quote:

path = u_getDataDirectory();
KPrintF("u_getDataDirectory = %s\n",path);


Then it return PROGDIR/Resource, just like u_getDataDirectory return wrong path already. But then, if at end of u_getDataDirectory, i add:

Quote:

u_setDataDirectory(path);
KPrintF("path at end of u_getDataDirectory = %s\n", path);
return gDataDirectory;


Then it print normal path (i.e. PROGDIR:Resource), but when UDataPathIterator::UDataPathIterator call it at begining path aready PROGDIR/Resource. What mean that "return gDataDirectory" from u_getDataDirecotry return bad path.

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@Fab
Are you tried to update to latest curl already ? I have some problem with certificates when i build 7.34.0 for odyssey 1.23. Problem is: with Security/Ignore SSL errors everything works, i can go on https fine. But if i untick that option, i have on every https site:

Quote:

Unable to open 'http://sitename".
Error 60: Peer certificate cannot be authenticated with give CA certificates.


But, i have of course your latest curl-ca-bundle.crt (and in Settings/Secutiry certificate path are have "PROGDIR:curl-ca-bundle.crt" as well.

I even tried with my own: i.e. in the curl 7.34.0 directory i run "make ca-bundle" and copy new lib/ca-bundle.crt to the odyssey directory instead of your old one : still the same error.

Have any ideas what can be wrong ? By default even with curl binary it is:

Quote:

7/0.RAM Disk:> ls -la curl#?
-rwx------ 1 root wheel 2991660 2014-02-06 12:23 curl
-rwx------ 1 root wheel 229047 2014-02-06 12:23 curl-ca-bundle.crt

7/0.RAM Disk:> curl https://google.com
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.

7/60.RAM Disk:>


And i need to add --cacert option to it to make it works:

Quote:


7/0.RAM Disk:> curl --cacert curl-ca-bundle.crt https://www.google.com

<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>302 Moved</TITLE></HEAD><BODY>
<H1>302 Moved</H1>
The document has moved
<A HREF="https://www.google.ru/?gws_rd=cr&e ... g">here</A>.
</BODY></HTML>

7/0.RAM Disk:>


Go to top
Re: Odyssey 1.23 progress
Just popping in
Just popping in


See User information
@kas1e

Mmh, no idea, i built Odyssey with Curl 7.34 and OpenSSL 1.0.1f, and i don't have such issue.

I'd say your curl build doesn't find the proper ca bundle file anymore, especially since it works if you specify it with an option.

Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@Fab
I see they release few days ago 7.35.0 , there is few fixes to openssl, dunno through if related.

Did you build libcurl with providing name of ca bundle file or something ?

Btw, what i can notice beetwen binaries from curl 7.21.7 and from 7.34.0 , is that while they return same openssl errors, output a bit different:

i.e. 7.21.7 says:

Quote:


ram:> curl_7_21_7 https://www.google.com

curl: (60) SSL certificate problem, verify that the CA cer is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed.
More details here: htt://curl.haxx.se/docs/sslcerts.html


But with curl 7.34.0 binary:

Quote:

7/0.RAM Disk:> curl https://google.com
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html


Dunno through if it related too, just some difference in output.

Will try 7.35.0 for now just in case.


Btw, my configure line is:

Quote:

./configure --build=i686-pc-cygwin --host=ppc-amigaos --disable-shared --enable-static --disable-dependency-tracking --enable-threaded-resolver \
--disable-ntlm-wb --disable-ipv6 --disable-debug --disable-curldebug --without-random LIBS=-lpthread


Which in end give me:

Quote:

curl version: 7.35.0
Host setup: powerpc-unknown-amigaos
Install prefix: /usr/local
Compiler: ppc-amigaos-gcc
SSL support: enabled (OpenSSL)
SSH support: no (--with-libssh2)
zlib support: enabled
GSSAPI support: no (--with-gssapi)
SPNEGO support: no (--with-spnego)
TLS-SRP support: no (--enable-tls-srp)
resolver: POSIX threaded
ipv6 support: no (--enable-ipv6)
IDN support: no (--with-{libidn,winidn})
Build libcurl: Shared=no, Static=yes
Built-in manual: no (--enable-manual)
--libcurl option: enabled (--disable-libcurl-option)
Verbose errors: enabled (--disable-verbose)
SSPI support: no (--enable-sspi)
ca cert bundle: no
ca cert path: no
LDAP support: no (--enable-ldap / --with-ldap-lib / --with-lber-lib)
LDAPS support: no (--enable-ldaps)
RTSP support: enabled
RTMP support: enabled (librtmp)
metalink support: no (--with-libmetalink)
HTTP2 support: disabled (--with-nghttp2)
Protocols: DICT FILE FTP FTPS GOPHER HTTP HTTPS IMAP IMAPS POP3 POP3S RTMP RTSP SMTP SMTPS TELNET TFTP

SONAME bump: yes - WARNING: this library will be built with the SONAME
number bumped due to (a detected) ABI breakage.
See lib/README.curl_off_t for details on this.


I.e. i have "ca cert bunde: no". I can of course specifcy --with-ca-bundle=curl-ca_bundle.crt , but then, i was in hope that if we have it in security/path its enough ?

Go to top
Re: Odyssey 1.23 progress
Just popping in
Just popping in


See User information
@kas1e

You have to specify the bundle location, it won't default to "PROGDIR:curl-ca-bundle.crt" magically. IIRC, it should be CURL_CA_BUNDLE define in config.h

I don't know about the configure options, i made my own makefile/config.h for curl, i don't need their configure crap.

Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@Fab
For now just build curl with --with-ca-bundle=ca_bundle.crt, and it takes from progdir fine and all works.

Yep, i can just now redefine CURL_CA_BANDLE to something like "PROGDIR:curl-ca-bundle.crt", but then i can't get why you need to have that settings/preferences/security/certificated_path, if, it will be anyway taken only from PROGDIR:curl-ca-bunlde.crt, as it hardcore in curl, and does not matter what to write here, it still will search for PROGDIR:curl-ca-bundle.crt.

I mean, if it there just to show where file placed, then imho it should't be selectable, as it seems will make no differences ?

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Odyssey 1.23 progress
Just popping in
Just popping in


See User information
@kas1e

The crt path option of course works too in Odyssey. It may be another issue in your curl build. But first we had to rule out other potential issues by setting default path properly.

Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@Fab
Quote:

But first we had to rule out other potential issues by setting default path properly.

Ok, done with PROGDIR:curl-ca-bundle.crt by editing related config.h and CURL_CA_BUNDLE define, and it works. But, if i rename that file to something like omega1200.crt , and choice it from odyssey's settings in secirity path (so its PROGDIR:omiga1200.crt), then save / quit /run odyssey, then that file didn't taken in account and when i go to any https page i have:

Quote:

Unable to open "https://sitename"
Error 77: Problem with SSL CA cert (path? access rights?)


Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@Fab
Good (or bad) news: in morphos's 1.23 version its the same didn't works. I.e. i rename file to omega1200.crt, choice that file in security path, save, quit, run, go to https page , and it give me same error as on os4. Once i rename file back to curl-ca-bundle.crt, but still in security path have omega1200.crt, then it all start to works.

That what i mean before: path + file inbuild in curl library, so seems does not matter what we set on os4 port, or on morphos version in that path, it just didn't taken in account on all versions anymore.

Go to top
Re: Odyssey 1.23 progress
Just popping in
Just popping in


See User information
@kas1e

The related code setting the path from settings probably got erased by a merge at some point in curl backend file. Trivial to fix.

Anyway, with defaults settings in CURL, it works fine, which is what matters most.

Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@Fab
Quote:

Anyway, with defaults settings in CURL, it works fine, which is what matters most.


Yep, so i leave it as it now and will add other os4specific parts.


Edited by kas1e on 2014/2/6 13:37:40
Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@all
Native mouse wheel support added, feels better (typing from 1.23)

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@kas1e

Roman, the autoscroll button are now visible in 1.23 ?

I mean that one: http://cdn.howtogeek.com/wp-content/uploads/2008/03/image136.png

Because in current 1.16 is not visible but we need one..


Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@samo
I don't know what is it and where it should be. Where it is on morphos version ? How i can see it in 1.9 port ?

Go to top
Re: Odyssey 1.23 progress
Just popping in
Just popping in


See User information
You can enable autoscrolling by doubleclicking middle mouse button. In that case, a "move" cursor is shown.

Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@Fab
Not here currently, i assume once will add native mouse pointers then.

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Odyssey 1.23 progress
Home away from home
Home away from home


See User information
@all
Some video of youtube in action:
http://www.youtube.com/watch?v=Q4QfMfFxaS8

Checked also html5test.com, scored 420 points (same as on mos).

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top

  Register To Post
« 1 ... 4 5 6 (7) 8 9 10 ... 72 »

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )



Polls
Running AmigaOS 4 on?
AmigaOne SE/XE or microA1 12% (26)
Pegasos2 3% (8)
X5000 22% (48)
X1000 14% (30)
A1222 8% (19)
Sam 440/460 18% (40)
Classic PowerPC Amiga 2% (6)
WinUAE emulation 7% (16)
Qemu emulation 9% (21)
Total Votes: 214
The poll closed at 2025/12/1 12:00
7 Comments


Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project