Closed Bug 22673 Opened 25 years ago Closed 24 years ago

missing -lgtk -lgdk in mailnews/compose/tests

Categories

(MailNews Core :: Backend, defect, P3)

Product:
MailNews Core
Component:
Backend
Platform:
Other
BSDI
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: lidl, Assigned: granrosebugs)

Details

(Keywords: verifyme) 

When building the mozilla from source, I get build
failures on BSD/OS due to an unresolved gtk systems
for the mailnews/compose/tests/{compose2,sendlater}
directories.

Editting the generated Makefiles to have a -lgtk -lgdk
after the -lraptorgfx allows the build to complete.
The configure build system probably needs to add the
appropriate toolkit libraries on the link line when
building with gtk as the toolkit.

If you examine the full build log for BSD/OS 4.0.1 in
the ports directory, you will see the same error message:


-Kurt
This looks like a "Build Config" issue... but the "Build Config" component
only appears in the Browser Product. Leaving in MailNews at present.

It seems there are other bugs about gtk library problems in that component,
some causing crashes on other *nixes; the fixes for those may fix this problem,
or this problem may best be fixed while fixing one of those... don't know.

CC-ing cyeh@netscape.com
Assignee: phil → cyeh
reassign to cyeh then.
I'll cc: leaf
Assignee: cyeh → granrose
reassign to granrose. can you take a look at this?
Status: NEW → ASSIGNED
Target Milestone: M15
Sure.  I'm wary of hacking gtk issues with all the other issues I'm seeing in
other areas.  I'd also like to see what the decision is for dynamic vs static
linking on Solaris.
adding verifyme to keywords (so others can help) because I don't think I can 
verify this once the bug report is resolved.
Keywords: verifyme
Mass moving to M16 to get these off the M15 radar.  Please let me know if this
is really an M15 stopper.
Target Milestone: M15 → M16
Target Milestone: M16 → ---
Fix has been checked .in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
cool.  thanks chris!
                                                                                          
lidl@pix.net - can you help verify this?  We don't have builds on BSDI.  Thanks.
I have been using --disable-tests in my .mozconfig file for a
long time to work around this issue.  I just commented out that
and am doing the equivilent of a "clobber" build on the tree
that I last built.  (A CVS pull of the tip of the tree from
yesterday evening -- May 10, 2001.)

I'll post something else with the results of that build when it
finishes.
I was able to build a release completely without having to
use --disable-mailnews and --disable-tests.

I would consider this bug completely resolved.

verified fixed, per reporter's comments.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.