Opened 9 years ago

Closed 5 years ago

#1180 closed defect/bug (fixed)

build-errror on lauchpad

Reported by: jörg frings - fürst Owned by: KaZeR
Priority: critical Milestone: version 0.5.1
Component: core Version: git master
Severity: normal Keywords: cmake, autotools, build, launchpad
Cc: j.fringsfuerst@…

Description (last modified by usul)

Function `g_mutex_new_navit' implicitly converted to pointer at /build/buildd/navit-svn-5655-5/navit/support/glib/gatomic.c:913
Function `g_private_new_navit' implicitly converted to pointer at /build/buildd/navit-svn-5655-5/navit/support/glib/gslice.c:394
Function `g_mutex_new_navit' implicitly converted to pointer at /build/buildd/navit-svn-5655-5/navit/support/glib/gslice.c:395

Our automated build log filter detected the problem(s) above that will likely cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64.

This is often due to a missing function prototype definition.

Since use of implicitly converted pointers is always fatal to the application on ia64, they are errors. Please correct them for your next upload.

More information can be found at:

Attachments (1)

error-navit.txt (1.6 KB) - added by jörg frings - fürst 9 years ago.
errors from lauchpad build

Download all attachments as: .zip

Change History (11)

comment:1 Changed 9 years ago by jörg frings - fürst

  • Cc j.fringsfuerst@… added

comment:2 Changed 9 years ago by usul

  • Keywords cmake autotools build launchpad added; missing function prototype removed

comment:3 Changed 9 years ago by usul

Hi Jörg, thanks for your report!

Sadly I'm not sure, if I'm experienced enough with compiling to understand all details. So this problem is indipendend from autotools and cmake?

comment:4 Changed 9 years ago by usul

  • Description modified (diff)

comment:5 Changed 9 years ago by tryagain

What architecture is that build for?

Glib copy shipped with navit is used on systems which lack native glib. Those are mobile platforms and, probably, Windows.

I'm unsure if we should fix this bug unless we're going to support one of above platforms in x64 mode.

If above report is from some desktop linux distribution, i guess there's wrong build system configuration (missing glib-devel package?).

Please report more details, supplying us with full configuration and build logs link would be nice.

comment:6 Changed 9 years ago by jörg frings - fürst


first sry for my late answer:

  • is was build for amd64 and i386.
  • both builds runs without errors,
  • the debs were produced, but not copied

so everything is ok

But in the last step three warnings are considered as critical errors (see error-navit.txt).

My first idea was that pthread_mutex_t is not defined

But it is.


Changed 9 years ago by jörg frings - fürst

errors from lauchpad build

comment:7 Changed 9 years ago by tryagain

I was asking you to attach or link the full configuration and build logs.

I think I have found one myself, at

Please compare your setup and logs, with any successful launchpad navit build, for example, to

Search for the "--->>> support" phrase on both logs. On linux, you should have "Disabled glib ( native Glib found )" phrase, not "Enabled glib ( Glib not found )". That difference makes navit build to use source file which is not intended for full-scaled linux distributions. You probably have not satisfied all the dependencies.

Another notable difference is that your build reports "Could NOT find PkgConfig? (missing: PKG_CONFIG_EXECUTABLE)" while the working one says "Found PkgConfig?: /usr/bin/pkg-config (found version "0.26")".

So please recheck the dependencies.

Last edited 9 years ago by tryagain (previous) (diff)

comment:8 Changed 7 years ago by kazer

Hi Jörg,

Can you please provide an update for this ticket?


comment:9 Changed 7 years ago by jörg frings-fürst


sorry I don't work any more at lauchpad / ubuntu.

At my private debian repro it works fine. So I think you can close this bug.

CU Jörg

comment:10 Changed 5 years ago by

  • Resolution set to fixed
  • Status changed from new to closed

close because we have not enough informations

Note: See TracTickets for help on using tickets.