Package Details: lib32-glib 1.2.10-5

Git Clone URL: https://aur.archlinux.org/lib32-glib.git (read-only, click to copy)
Package Base: lib32-glib
Description: Common C routines used by Gtk+ and other libs (32-bit)
Upstream URL: http://www.gtk.org/
Licenses: LGPL
Submitter: prg
Maintainer: prg (bennofs, FabioLolix)
Last Packager: prg
Votes: 16
Popularity: 0.000076
First Submitted: 2015-12-15 03:35 (UTC)
Last Updated: 2022-03-07 18:43 (UTC)

Latest Comments

1 2 Next › Last »

FabioLolix commented on 2023-06-18 15:40 (UTC)

Hello, there is no need to specify gcc-multilib since gcc 7.2.1 (Nov 2017), instead this need a makedepends on lib32-gcc-libs otherwise it won't build in clean chroot

checking whether the C compiler works... no
configure: error: in `/build/lib32-glib/src/glib-1.2.10':
configure: error: C compiler cannot create executables
See `config.log' for more details

prg commented on 2022-03-07 18:44 (UTC)

Thanks @MarsSeed! pkgver 5 should address glib.install and the C(XX)FLAGS

MarsSeed commented on 2022-03-05 16:32 (UTC)

And then you can remove the glib.install file as suggested here. ;)

MarsSeed commented on 2022-03-05 16:30 (UTC)

Or you can make the build work even with the defaults shipped by Arch.

All you have to do is add the following export lines inside the PKGBUILD's build() function, at the beginning of it:

build() {
    export CFLAGS="${CFLAGS} -Wno-error -Wno-format -Wno-format-security"
    export CXXFLAGS="${CXXFLAGS} -Wno-error -Wno-format -Wno-format-security"

    # Keep the rest of the function intact
    # [...]
}

MarsSeed commented on 2022-03-05 16:03 (UTC)

Arch carries a wrong setting by default in /etc/makepkg.conf.

Wrong as in not suited to users, only to C/C++ developers and distro maintainers.

In CFLAGS=, -Wformat -Werror=format-security makes the build fail if the source code uses printf or scanf in a potentially memory-unsafe way.

That quoted section should be removed from makepkg.conf.

But inside CFLAGS='s quoted value, you can append -fstack-protector-strong. It will enhance the protections against some critical memory overflow vulnerabilities.

For me the lib32-glib build didn't fail because I have already removed the above mentioned section related to format-security.

prg commented on 2022-03-03 16:15 (UTC)

Not yet - I haven't gotten a chance to look into it. I think we can pass a gcc to flag to not treat that warning as an error

mr_cookie commented on 2022-03-03 05:32 (UTC)

@prg i get this following too,did you solved this problem?

testglib.c:904:3: error: format not a string literal and no format arguments [-Werror=format-security]
  904 |   g_print (string);
      |   ^~~~~~~
cc1: some warnings being treated as errors

prg commented on 2022-03-02 20:15 (UTC) (edited on 2022-03-02 20:16 (UTC) by prg)

@MarsSeed did you need to do anything to get this to compile properly? I get the following compilation errors even before removing the glib.install:

testglib.c:904:3: error: format not a string literal and no formatarguments[-Werror=format-security]
904 |   g_print (string);
    |
cc1: some warnings being treated as errors

MarsSeed commented on 2022-03-02 19:59 (UTC)

Please kindly remove the glib.install file and the install=glib.install declaration from PKGBUILD.

$ namcap /var/cache/pacman-local/pkg/lib32-glib-1.2.10-4-x86_64.pkg.tar.zst

lib32-glib W: .INSTALL file runs a command provided by hooks.

texinfo, which is part of the group base-devel, contains the needed post-install, post-upgrade and post-remove hooks now.

Also, the included .INSTALL script fails:

:: Processing package changes...
(1/1) installing lib32-glib
error: command failed to execute correctly

1 2 Next › Last »