Opened 7 years ago

Closed 5 years ago

Last modified 9 months ago

#8579 closed bug (fixed)

NetPositive don't start anymore

Reported by: X512 Owned by: axeld
Priority: normal Milestone: R1
Component: Kits/Mail Kit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #10403
Has a Patch: no Platform: All

Description

This is hrev44133

Tracker says that following symbol is not found:

encode_base64__FPcT0x

Change History (9)

comment:1 Changed 7 years ago by diver

Component: - GeneralKits/Mail Kit
Owner: changed from nobody to czeidler

hrev43382/hrev43383 might be responsible for this.

comment:2 Changed 7 years ago by czeidler

Cc: axeld@… added

actually I don't know, is export not needed?

comment:3 Changed 7 years ago by jackburton

You have to add 'extern "C"' in the function declaration, now that the code is contained in a cpp file.

comment:4 Changed 7 years ago by anevilyak

Cc: axeld@… removed
Owner: changed from czeidler to axeld
Status: newassigned

hrev43383 is the culprit indeed, assigning to Axel.

comment:5 Changed 7 years ago by X512

As I understand NetPositive requires C++ version of encode_base64, not 'extern "C"'. NetPositive with libmail.so from BeOS is working.

comment:6 Changed 7 years ago by anevilyak

Looking further, R5's mail kit's declaration for encode_base64() does not have the headerMode parameter that ours does. Nor do we declare an equivalent or an extern symbol matching that one. Could be the problem, but what's puzzling is that it's been this way for ages, and Axel's commit didn't change that AFAICT.

comment:7 Changed 6 years ago by waddlesplash

This is still a problem. Neither NetPositive nor BeOS Mail works because of missing decode/encode base64 functions.

comment:8 Changed 5 years ago by pulkomandy

Blocking: 10403 added

(In #10403) The encode_base64 issue is #8579. Please open a dedicated ticket for each remaining issue (if any), that will be simpler to track.

comment:9 Changed 5 years ago by pulkomandy

Resolution: fixed
Status: assignedclosed

Fixed in hrev46905. It now hits memory corruption when trying to access a website, however.

Note: See TracTickets for help on using tickets.