Opened 9 years ago

Closed 9 years ago

#6439 closed bug (fixed)

Build problem: skipped IMAP for lack of imap_client.o...

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

Description

I was trying to build haiku from haiku. The sources from yesterday. It is failing to build because warnings are being treated as errors and the above in the summary. I will attach a file with Terminal output.

Attachments (1)

Haiku_Build_Problem_Terminal_Output.txt (5.1 KB) - added by HAL 9 years ago.
Terminal output

Download all attachments as: .zip

Change History (12)

Changed 9 years ago by HAL

Terminal output

comment:1 Changed 9 years ago by HAL

I was building hrev37982 gcc4 hybrid on hrev37730 gcc4 hybrid.

comment:2 Changed 9 years ago by anevilyak

Component: Build SystemKits/Mail Kit
Owner: changed from bonefish to bga
Version: R1/alpha2R1/Development

comment:3 Changed 9 years ago by HaikuBot

I got same error. Maybe we should comment this:

1260 EnableWerror src add-ons mail_daemon ;

(taked from here http://dev.haiku-os.org/browser/haiku/trunk/build/jam/BuildSetup)

comment:4 Changed 9 years ago by anevilyak

The correct thing to do would be to fix the warning.

comment:5 in reply to:  4 ; Changed 9 years ago by siarzhuk

Replying to anevilyak:

The correct thing to do would be to fix the warning.

Hm... All my life I thought that having consistent, non-broken build is the high-priory task for cooperative software development work. Do you want to say that warnings squashing is much more urgent task? :-D

comment:6 in reply to:  5 ; Changed 9 years ago by anevilyak

Replying to siarzhuk:

Hm... All my life I thought that having consistent, non-broken build is the high-priory task for cooperative software development work. Do you want to say that warnings squashing is much more urgent task? :-D

No, I was saying the correct thing to do would be to fix the build by fixing the warning, since they mean the same thing in this context. Oddly that particular one seems to be compiler-specific though, I'm not seeing it on any of my machines on either FreeBSD or Haiku as build host.

comment:7 in reply to:  6 ; Changed 9 years ago by mmadia

Replying to anevilyak:

Replying to siarzhuk:

Hm... All my life I thought that having consistent, non-broken build is the high-priory task for cooperative software development work. Do you want to say that warnings squashing is much more urgent task? :-D

No, I was saying the correct thing to do would be to fix the build by fixing the warning, since they mean the same thing in this context. Oddly that particular one seems to be compiler-specific though, I'm not seeing it on any of my machines on either FreeBSD or Haiku as build host.

Right, and Build-O-Matic (also running on FreeBSD 8) hasn't mentioned anything. Would anyone be willing to install the native GCC 4.4.4 package on Haiku and seeing if the error persists?

comment:8 in reply to:  7 Changed 9 years ago by HaikuBot

Replying to mmadia:

Right, and Build-O-Matic (also running on FreeBSD 8) hasn't mentioned anything. Would anyone be willing to install the native GCC 4.4.4 package on Haiku and seeing if the error persists?

I used GCC 4.3, seems I should try 4.4.4?

comment:9 Changed 9 years ago by anevilyak

Owner: changed from bga to anevilyak
Status: newin-progress

comment:10 Changed 9 years ago by anevilyak

Fixed in hrev38075.

comment:11 Changed 9 years ago by anevilyak

Resolution: fixed
Status: in-progressclosed
Note: See TracTickets for help on using tickets.