Re: Launchpad i386 build: Memory exhausted
2018-02-16 11:37 GMT+01:00 Colin Watson <cjwat...@ubuntu.com>: > On Fri, Feb 16, 2018 at 09:21:56AM +0100, Cesare Falco wrote: > > I'm packaging latest MAME 0.194 and it builds fine on my PPA. > > Unfortunately, link fails for i386 due to virtual machine memory issues: > > > > /usr/bin/ld: final link failed: Memory exhausted > [...] > > Does anyone know whether virtual machines for official Ubuntu releases > have > > more resources, specifically more memory? > > PPA builds and Ubuntu builds use 100% identical virtual machines. > > Anyway, it's not that the virtual *machine* is out of memory; it's that > any single 32-bit process can only address a certain amount of that > memory. As far as I'm aware, there's no option but to continue trying > to persuade the linker to take less memory. > > Mame 0.195 has been released in the meantime. I experimented lots of tweaking and they all led me nowhere. :-( The resulting executable is *big* indeed, and this is the definitive issue. :-/ I'm asking everyone for advice: assuming that no i386 build seems possible any more, should I: - stop maintaing Mame - remove i386 from the supported archs - ... (any suggestion is welcome here!) Thank you all in advance, have a nice day! Cesare -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Launchpad i386 build: Memory exhausted
Hello everyone, I'm packaging latest MAME 0.194 and it builds fine on my PPA. Unfortunately, link fails for i386 due to virtual machine memory issues: /usr/bin/ld: final link failed: Memory exhausted You can find a full log for build here: https://launchpadlibrarian.net/357194916/buildlog_ubuntu-artful-i386.mame_0.194+dfsg.1-0ubuntu1~ppa2~artful1_BUILDING.txt.gz and also here in case I got struck by the greatest idea and try a new build :) https://pastebin.com/dZLResCK Please note I've already put great care in tweaking linker options to reduce memory consumption, with no luck. I've already faced this issue in backporting, but it never occured with current release. It's worth noting that the default compiler in Artful (gcc 7) is also the recommended compiler by upstream developers, so forcing a different release doesn't look an option either. It would be nice to have a working i386 build on my PPA, but what I care more is uploading Mame 0.194 to Bionic. Does anyone know whether virtual machines for official Ubuntu releases have more resources, specifically more memory? Should I try uploading the tarball and see? What happens if I get the same memory issue, would I be able to downgrade to 0.193? I'm looking forward for any kind advice, thank you in advance! :) Cheers, Cesare -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Error linking i386 build on Launchpad
2016-01-11 13:40 GMT+01:00 Colin Watson <cjwat...@ubuntu.com>: > On Mon, Jan 11, 2016 at 11:46:24AM +0100, Cesare Falco wrote: > > I'm not able to build the current release of Mame on Launchpad due to > > memory issues: > > > > /usr/bin/ld: failed to set dynamic section sizes: Memory exhausted > > > > Did anyone find any workaround? Is there any way to tell Launchpad I > need a > > VM with more memory? Or perhaps I can force the build on a specific > machine > > which has more memory? > > There are various linker options which can help reduce memory taken > while linking, e.g. -Wl,--no-keep-memory, -Wl,--reduce-memory-overheads, > or -Wl,--hash-size=NUMBER. I can't quite tell what you're doing right > I've tried many combinations and ended up setting them all, with NUMBER being as little as 2, but with no luck. :( In the meantime, a new upstream version popped out; the latest build log is here: https://launchpad.net/~c.falco/+archive/ubuntu/alpha/+build/8920070/+files/buildlog_ubuntu-wily-i386.mame_0.170-0ubuntu1~ppa1~wily1_BUILDING.txt.gz > now because your build hides the exact command lines in use (please > reconsider that), but have you looked into those? > I enabled the verbose build which no longer hides the command lines. This produces a *big* file i.e. several megabytes: should I keep it anyway once the issue is solved? I thought it advisable to limit the building output, isn't it? Thank you! Cesare -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Error linking i386 build on Launchpad
Hello all! I'm not able to build the current release of Mame on Launchpad due to memory issues: /usr/bin/ld: failed to set dynamic section sizes: Memory exhausted see full build log here: https://launchpadlibrarian.net/232540518/buildlog_ubuntu-wily-i386.mame_0.169-0ubuntu1~ppa5~wily1_BUILDING.txt.gz This only happens on i386, amd64 builds fine. I've been searching around, but the only solution seems to give more memory to the virtual machine. I've also asked for help on Launchpad itself, but no answer so far: https://answers.launchpad.net/launchpad/+question/280517 I know the resulting binary *is* big, but there are other big project out there, I guess someone else may have been stumbled upon the same issue. Did anyone find any workaround? Is there any way to tell Launchpad I need a VM with more memory? Or perhaps I can force the build on a specific machine which has more memory? Thank you in advance, all the best! Cesare -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Follow Up from Let's Discuss Interim Releases
1. Move to a rolling release similar to what I proposed in the original straw man. 2. Continue to release interim releases but only support them until roughly the next interim release 6 months later. 3. Dramatically increase the rate of our releases to, say, once per month. I think there's another proposal worth considering IMHO, quoting Alex Chiang's e-mail: Let's figure out how to decouple and disentangle our apps from our platform. I understand the main issue is that nearly nobody offers packages for Ubuntu upstream, anyway the idea of splitting the distro into, say, ubuntu-sys and ubuntu-apps with different devel cycles is both new and intriguing. My 2 cents. Cesare. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Automatic import from debian package not found in Ubuntu
Is it because the package sits in the non-free section of the Debian Archive ? No, it's not. The problem was that our auto-sync script said this: [New] mess_0.146-1 No previous publications in Ubuntu OK (Y/n)? * Trying to add mess ... mess_0.146-1 is trying to override modified binary mame-tools_0.145-0ubuntu1. OK (y/N)? ... and I didn't have a chance to check whether this was OK. Can you say whether mess 0.146-1 completely supersedes mame 0.145-0ubuntu1, or are there outstanding Ubuntu changes that we'd need to preserve by way of a merge? mame 0.146-2 has already anything needed for merging, but I guess it requests manual sync to override my previous package in the repository. Is this right? Cheers, Cesare. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
