extra -lc in generated build files [Re: [solved] chromium doesn't open any page]

Evan Martin evan at chromium.org
Sun Apr 17 18:46:27 UTC 2011


On Sun, Apr 17, 2011 at 11:38 AM, Baptiste Daroussin <bapt at freebsd.org> wrote:
>> I am responsible for the code that generates the .mk files.  Can you
>> paste the area around the file that contains the -lc flag?  I will
>> help diagnose where it's coming from.
>
> Here they are:
>
> app/app_unittests.target.mk.bak:        -lc \
> chrome/automated_ui_tests.target.mk.bak:        -lc \

Hm, it seems most likely that we're picking that up from a pkg-config file.

Can you try something like:

$ grep -- -lc /usr/lib/pkgconfig/*

(you might need to adjust the paths, I'm on Linux, sorry)
to see if any libraries we use are including it?

You can see the list of packages imported via pkg-config by looking at
build/linux/system.gyp in the Chrome tree.

$ grep libs-only-l build/linux/system.gyp
              '<!@(<(pkg-config) --libs-only-l gtk+-2.0 gthread-2.0)',
              '<!@(<(pkg-config) --libs-only-l gtk+-unix-print-2.0)',
                  '<!@(<(pkg-config) --libs-only-l nss | sed -e "s/-lssl3//")',
                  '<!@(<(pkg-config) --libs-only-l nss)',
              '<!@(<(pkg-config) --libs-only-l freetype2)',
              '<!@(<(pkg-config) --libs-only-l fontconfig)',
              '<!@(<(pkg-config) --libs-only-l gdk-2.0)',
              '<!@(<(pkg-config) --libs-only-l gconf-2.0)',
              '<!@(<(pkg-config) --libs-only-l x11)',
            '<!@(<(pkg-config) --libs-only-l xi)',
              '<!@(<(pkg-config) --libs-only-l xext)',
                  '<!@(<(pkg-config) --libs-only-l gnome-keyring-1)',
          '<!@(<(pkg-config) --libs-only-l dbus-glib-1)',
              '<!@(<(pkg-config) --libs-only-l ibus-1.0)',


More information about the freebsd-chromium mailing list