[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#735182: RFS: fuseloop/1.0.1-1 ITP -- loopback mount using FUSE



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/22/2014 05:12 AM, Johannes Schauer wrote:

> Hi,
> 
> Quoting أحمد المحمودي (2014-01-22 10:36:11)
> 
>> Actually what happens implicitly (at least on Ubuntu precise) is:
>> $(CC) $(CFLAGS) $(LDFLAGS) $^ -o $@
>> 
>> which causes the compilation to fail, because the -l<...> should be
>> after the object files (or source files in this case).
> 
> Ah funny, so it's a ubuntu problem. I did not observe this problem
> with Debian unstable.
> 
> After trying it out myself in a ubuntu precise and saucy chroot and
> asking on #debian-mentors, the reason why this error happens only on
> Ubuntu seems to be:
> 
> https://wiki.ubuntu.com/ToolChain/CompilerFlags#A-Wl.2C--as-needed
> https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition
> 
> Should I contact upstream to yet again change his makefile or are
> things okay as they are because everything works fine in Debian?

Do things still work fine in Debian when using ld.gold (by installing
the binutils-gold package) rather than ld.bfd? I know there's an
important difference in ld.gold related to --as-needed (or possibly to
- --no-as-needed, I don't recall offhand).

I seem to recall that there are long-term plans to switch Debian over to
ld.gold or to produce the same effect in ld.bfd, and that it's
recommended (or at least preferred) to make sure your package builds
with the gold linker; I suspect that this is the "similar change...
being discussed for Debian" mentioned in the ToolchainTransition article
you linked.

There's no expected completion date for this AFAIK, but trying to be
compliant with it isn't a bad idea; I've already got the upstream of
something I haven't even packaged yet to accept a compliance patch, just
based on test packaging attempts.

- --
   The Wanderer

Secrecy is the beginning of tyranny.

A government exists to serve its citizens, not to control them.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJS39JJAAoJEASpNY00KDJrqYQP/0GBnMOtwgXJwbDIj/qskRr0
En2lnuVM76ua/xb4iYCrbmeQ3APnwJ8pqrJ2oSozuA+A1244TAiXgzf/iLFCZ+JI
2sID3uMLf8+rrXnVs0FFKNEuNHAVYLSi9TxF1Ptlpai1YFwasGU5MrEr13kthrD+
RgQ0+3HWxJ29aNo4yR90SxK8zADjjm0bggJlwI8ltGaWxKMPZsfZSs12f19lMSe+
UpIT0vISg724mlsU3i31+rUIrfnAm+AlrVzX0j5H6p5gkp6o1+IKsmi9LBQviCJh
sBZ85Eq7LvZpfWpErf1FBXVRlnosuBC/P/S8XfJhTQP5owDLqOO5ot33IKb128f0
/MmoiT0xe/KjlKnqcLg0Mru90HmNkm1VY0ZKuojJfc1n/OcMg+IX8UrjGCTSnjSW
bV7CpT2eYFj6ikbSNcLGBWEy+zllppWaBXIB5K+c3NJ++oc1VHN88/lKlmL36d07
BKPiMA1qoyGbdbpr9dLbCXL8QVgOS9ZblMXRimZjsYhDDM4DzZq6pMheTorfCUR3
9wzGL40K1tE4MNm/j2gfKaYTKauw1u+EI70CPX6+jFECmWqAsL0grDHvMlavZfvN
JmoxhwsH6WHldkrhjih1VcglJ84AZCB/wllxsRRI0+ULt7yo4X7966y+0AFi57la
5xw2Zvg+Asg22VMaA1cy
=AeaL
-----END PGP SIGNATURE-----


Reply to: