Opened 14 years ago
Closed 14 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: | ||
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)
Change History (12)
by , 14 years ago
Attachment: | Haiku_Build_Problem_Terminal_Output.txt added |
---|
comment:2 by , 14 years ago
Component: | Build System → Kits/Mail Kit |
---|---|
Owner: | changed from | to
Version: | R1/alpha2 → R1/Development |
comment:3 by , 14 years ago
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)
follow-up: 6 comment:5 by , 14 years ago
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
follow-up: 7 comment:6 by , 14 years ago
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.
follow-up: 8 comment:7 by , 14 years ago
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 by , 14 years ago
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 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | new → in-progress |
comment:11 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | in-progress → closed |
Terminal output