Le 06/03/2017 03:17, Lucas C. Villa Real a écrit :
> 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 [1]
I tried EditRecipe MC with
- ftp.midnight-commander.org/mc-4.8.18.tar.xz [1]
- 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 [2]. 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 [2].
What puzzle me is that it didn't resolve the right url after I fixed the
recipe.
> 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.)
I will see what I can do.
Regards,
--
Stéphane Aulery
Links:
------
[1] ftp://ftp.midnight-commander.org/mc-4.8.18.tar.xz
[2] http://gobolinux.org
_______________________________________________
gobolinux-users mailing list
[email protected]
http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
