Re: gobolinux-users Digest, Vol 140, Issue 8
sali <[email protected]> Mon, 06 Mar 2017 06:40:39 +0000
| Newsgroups | gmane.linux.distributions.gobo.general |
|---|---|
| Message-ID | <[email protected]> |
[email protected] schreef op 2017-03-06 02:26: > Send gobolinux-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.gobolinux.org/mailman/listinfo/gobolinux-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of gobolinux-users digest..." > > > Today's Topics: > > 1. Re: gobolinux-users Digest, Vol 140, Issue 5 (Lucas C. Villa > Real) > 2. Re: gcc Internal Compiler Errors (Lucas C. Villa Real) > 3. Re: gobolinux-users Digest, Vol 140, Issue 5 (Lucas C. Villa > Real) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 5 Mar 2017 23:07:56 -0300 > From: "Lucas C. Villa Real" <[email protected]> > To: "[email protected]" > <[email protected]> > Subject: Re: [gobolinux-users] gobolinux-users Digest, Vol 140, Issue > 5 > Message-ID: > <CAAvzgtZdMmWrFdf4b82dXMyHhJiE+fyqQhsRdPrhAo=zyw8Zww@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Sun, Mar 5, 2017 at 10:20 PM, Stéphane Aulery <[email protected]> wrote: > >> Le 06/03/2017 à 01:24, Lucas C. Villa Real a écrit : >> >>> On Sun, Mar 5, 2017 at 8:23 PM, Stéphane Aulery <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Le 06/03/2017 à 00:15, sali a écrit : >>> >>> >>> The Program is still there. >>> Only the symlinks are removed. >>> What I did was: make one symlink >>> from >>> /Programs/GMP/6.1.1/lib/libgmp.so.10.3.1 >>> to >>> /System/Index/lib/libgmp.so.10 >>> 'by hand'. >>> That should be enough. >>> >>> >>> Thanks. Lucs gave me a commanl which worked well : >>> >>> SymlinkProgram -c overwrite GMP 6.1.2 >>> >>> >>> Great to know! >>> >>> >>> After that I could compile GMP and GCC. Just after the >>> compilation >>> of GCC it proposed me to compiler Linux. I did it. No compilation >>> problem but now the configuration of the linux console passed to >>> the >>> kernel which makes the definition is rough. >>> >>> Did you have the same problem? >>> >>> >>> I'm not sure I understand your last sentence. >>> >> >> Sorry, my english is awfull. >> > > So is mine, no worries. I wish I had taken my French lessons more > seriously > in the past so we could get past language slips :) > > >> Are you talking about the >> >>> "menuconfig" interface that's shown when you Compile Linux? If that's >>> what you mean, then it's safe to click on "Exit" without making any >>> changes; the kernel should be built just fine afterwards. Or do you >>> need >>> some clarification about the arguments passed by GRUB to boot the new >>> kernel? >>> >> >> I think that arguments passed to GRUB for the new kernel have been >> altered >> during compilation / installation. I could check that. > > > If you have an EFI system (which you can tell based on the presence of > /sys/firmware/efi/), then "Compile Linux" attempts to update the GRUB > application that is loaded at boot time. If for some reason it failed > to > update it, then you will be left with a file at > /System/Kernel/Boot/BOOTX64.EFI. Once you mount your EFI System > Partition > and replace the its BOOTX64.EFI file under /BOOT/EFI with the one under > /S/K/Boot, the updated kernel will be recognized on the next boot. > > The patch release (016.01) that we're working on should fix issues with > the > auto-mounting of the EFI System Partition so that kernel updates go > more > smoothly. > > Merci, > Lucas > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.gobolinux.org/pipermail/gobolinux-users/attachments/20170305/b74d04d7/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Sun, 5 Mar 2017 23:17:09 -0300 > From: "Lucas C. Villa Real" <[email protected]> > To: "[email protected]" > <[email protected]> > Subject: Re: [gobolinux-users] gcc Internal Compiler Errors > Message-ID: > <CAAvzgtZ-OmHPCsHSfBDWBVdgb8kuGW3imDXmiHMuZ4VtTV+BsQ@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Sun, Mar 5, 2017 at 6:37 PM, Stéphane Aulery <[email protected]> wrote: > >> Le 28/02/2017 à 17:18, Lucas C. Villa Real a écrit : >> >> On Wed, Feb 22, 2017 at 7:30 PM, Stéphane Aulery <[email protected]> >> wrote: >> >>> Le 22/02/2017 à 19:59, Hisham Muhammad a écrit : >>> >>> We tracked down the problem. >>> >>> The version of GMP which the build of GCC built in the ISO for 016 >>> was >>> accidentally compiled for a higher processor family, so they are >>> incompatible with Core2 machines. >>> >>> We are rebuilding the packages for GMP and GCC to make them >>> processor-independent, so they run on all x86-64 systems. When we get >>> them ready to install, I'll post about it here. >>> >>> >>> Good news and thanks for you help. >>> >>> I'm happy to continue testing the distribution for my use. >>> >>> If I can do something for helping you, say it. >>> >> >> I have finally managed to rebuild and test the GMP and GCC packages. >> To >> upgrade: >> $ DisableProgram GMP >> $ InstallPackage GMP >> $ InstallPackage GCC >> >> Since GCC ships with a custom Environment file that updates >> system-wide >> CFLAGS, CXXFLAGS and LDFLAGS, I suggest that you invoke new instances >> of >> Compile under a new terminal so that the contents of the Environment >> cache >> are properly sourced. Alternatively, you may also run "source >> /System/Environment/Cache" once the two packages have been installed. >> >> Please let us know if the new packages will fix the problems you >> originally reported. >> >> >> It functioned. Just after the compilation of GCC it proposed me to >> compiler Linux. I did it. No compilation problem but now the >> configuration of the linux console passed to the kernel which makes >> the >> definition is rough. >> >> >> After a reboot I tried to compile Midnight Commander, and I have an >> error >> of ressource localisation. MC is not at >> >> - http://www.midnight-commander/dowsloads/mc-4.8.18.tar.xz >> >> but >> >> - ftp.midnight-commander.org/mc-4.8.18.tar.xz >> >> >> >> I tried EditRecipe MC with >> >> - ftp.midnight-commander.org/mc-4.8.18.tar.xz >> - http://ftp.midnight-commander.org/mc-4.8.18.tar.xz >> - ftp://ftp.midnight-commander.org/mc-4.8.18.tar.xz >> >> It is intractable : unable to resolve host address. >> > > Yeah, the server seems to be down. We have recently incorporated a > mirroring mechanism on gobolinux.org. The idea is to have it > automatically > fetch tarballs upon the submission of a new recipe. If the original > server > goes down, then Compile picks the tarball straight from gobolinux.org. > > Right now we haven't automated the whole thing -- we are manually > populating the mirror directory. We have to review our account settings > on > Dreamhost to buy more storage before we automate it. > > What I did right now was to manually populate the MC mirror with a copy > of > the tarball from another location. If you type "Compile MC" it should > work. > I have also created a binary package which you can install with > "InstallPackage MC". > > >> I tried also to compile XFE 1.42 I have an other error : >> >> checking for fxfindfox in -lFOX-1.6... no >> configure: error: "libFOX-1.6 not found" >> > > That's odd. My first installation of Fox ended up with an empty > include/fox-1.6 directory, and I got the same error trying to build > XFE. So > I removed Fox and recompiled it, which produced an include/fox-1.6 > packed > with files. > > There's something smelling with Compile and Runner when the package is > built as a dependency, it seems. I will investigate this. > > Anyhow, you can use the binary packages that I just produced -- just > type > InstallPackage Fox / XFE. > > >> >> I tried to compile GMP : good news, it succeded. >> > > Great! > > >> >> Have you a script to automate package building and test all recipes ? >> >> > We do not. I too feel that we lack some tools to detect broken recipes. > Writing one shouldn't be too difficult, but other priorities have > prevented > us from focusing on that task. > > A long time ago (9 years, it seems!) I sketched a simple CompileFarm ( > https://github.com/gobolinux/CompileFarm) to automate package building, > but > it went nowhere. Nowadays there are continuous integration tools that > we > could use to serve that purpose. > > Anyhow, we could start by testing which recipes have broken URLs and > which > do not. The whole recipes repository is available on Github already. > Something that iterates over all recipes and that runs "wget --spider" > should be enough to get a preliminary list. The next step would be to > have > that list available so that contributors could help us update our > mirror > directory. Please let me know if you'd like to volunteer to write such > a > tool (which seems an ideal candidate to be merged into our DevelScripts > package.) > > Best regards, > Lucas > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.gobolinux.org/pipermail/gobolinux-users/attachments/20170305/0dd8235e/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Sun, 5 Mar 2017 23:25:57 -0300 > From: "Lucas C. Villa Real" <[email protected]> > To: "[email protected]" > <[email protected]> > Subject: Re: [gobolinux-users] gobolinux-users Digest, Vol 140, Issue > 5 > Message-ID: > <CAAvzgtY_6jNgL5=+4opzk=AW_rKLx+_fFhHeBUJewuoGdUJBHA@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Sun, Mar 5, 2017 at 9:20 PM, Lucas C. Villa Real > <[email protected]> > wrote: > >> >> >> On Sun, Mar 5, 2017 at 8:15 PM, sali <[email protected]> wrote: >>> >>> @Stéphane Aulery >>> >> >> The Program is still there. >>> Only the symlinks are removed. >>> What I did was: make one symlink >>> from >>> /Programs/GMP/6.1.1/lib/libgmp.so.10.3.1 >>> to >>> /System/Index/lib/libgmp.so.10 >>> 'by hand'. >>> That should be enough. >>> >>> @Lucas >>> @Hisham >>> >>> Are you aware of the fact >>> that headers more often >>> than not are not installed >>> when using Compile ? >>> >>> I Found them back in >>> .local/Runner >>> so I was able to add them >>> after Install. >>> Or from Sources. >>> >>> Should I see them as >>> unmanaged files ? >>> Or is it just a glitz ? >>> >> >> That's a bug, for sure. Do you remember which program you were trying >> to >> build? I'd like to reproduce it on my side. >> > > I have just reproduced it. The problem seems to happen when Compile > asks if > you want to build some package "A" that's listed as a dependency of a > package "B". In that case, /Programs/A may end up with missing files. > If on > the other hand you type "Compile A" on the command line prior to > "Compile > B", then /Programs/A will be complete. > > I'm working on fixing this issue. I'll let you know when a fix is > available. > > Thanks, > Lucas > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.gobolinux.org/pipermail/gobolinux-users/attachments/20170305/2f3c412d/attachment.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > gobolinux-users mailing list > [email protected] > http://lists.gobolinux.org/mailman/listinfo/gobolinux-users > > > ------------------------------ > > End of gobolinux-users Digest, Vol 140, Issue 8 > *********************************************** @Lucas I think that's it. I was attempting to Compile first VLC and later Jack ( because of the dependencies ) to be able to Compile MuseScore. There was a chain of dependencies. Where the 'leftovers' started: libao libdvdread libdvdnav and so on. So maybe I'll start again an see what happens. And Thanks (!) Martin. _______________________________________________ gobolinux-users mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-users