553971 - With system sqlite3 build can use wrong JS-headers

Status: RESOLVED INCOMPLETE

(Thunderbird :: Build Config, defect)

Description

[Mikhail T.]

I'm trying to build thunderbird with the already built sqlite3 library -- its headers are in /opt/include on my system. I also have the headers from SpiderMonkey-1.6 in /opt/include.

Unfortunately, the build (in comm-1.9.1/mozilla/storage/src) constructs an erroneous compiler command-line -- along with sqlite3.h, the jspubtd.h is ALSO picked up from the /opt/include instead of from ../../dist/include/js.

The ../../dist/include/js should be ahead on the compiler's -I-list.

Comment 1

[Mark Banner (:standard8)]

Is this still a problem with Thunderbird 3.1 builds?

Comment 2

[Wayne Mery (:wsmwk)]

(In reply to comment #1)
> Is this still a problem with Thunderbird 3.1 builds?

Comment 3

[Mikhail T.]

Because this problem struck in the past, the FreeBSD port mail/thunderbird still uses SQLite3, that's bundled with the software instead of the standalone version (installed by the separate port databases/sqlite3).

I'll try patching up the port some time soon to attempt to use the already-installed sqlite3 and see, if the problem still exists... It, probably, does, if nothing was done to correct it...

Such bundling of various 3rd-party components into a single file is really a shame... It penalizes good systems (where 3rd-party software is easily installed) to help-out bad ones... By default thunderbird (and other Mozilla applications) should build with all of the non-Mozilla packages already installed.

Comment 4

[Mikhail T.]

Attachment: configure log

Output of configure script.

Comment 5

[Mikhail T.]

Attachment: Output of build log

Ok, there is definitely still a problem with the --enable-configure-foo, although I'm not sure, if sqlite is the "foo". As this build log shows, at some point, build picks up JavaScript headers from my /opt/include -- even though I did not ask for that (wanting to use those, that come bundled with Thunderbird).

The js*.h headers found in my /opt/include are those from SpiderMonkey-1.7.0, which some other package on my system (mediatomb) wants to use.

Comment 6

[Joshua Cranmer [:jcranmer]]

The build system has changed so much in nearly 4 years that this sort of request is effectively unactionable. If it's still a problem, this is likely to be a core build config issue.