Yep, sorry about that, it's been a busy week and I just hit reply without 
noticing it wasn't going to the list. My bad.

Mason Mullins

Sent from ProtonMail mobile

-------- Original Message --------
On Apr 8, 2018, 9:02 AM, Lucas C. Villa Real wrote:

> Hi Robert,
>
> Thanks for jumping in the topic! :)
>
> Mason forgot to copy the list on his latest reply; the problem has been fixed 
> with the installation of a new version of BinUtils.
>
> Regarding DocBook & Co., you're not alone. What helped me get past most of 
> the problems was to take some configuration bits from CentOS (which are 
> featured in 016.01).  Also, make sure that $XML_CATALOG_FILES includes 
> $goboVariable/lib/xml/catalog. That environment variable is set on 
> DocBook-XSL-Stylesheets/Current/Resources/Environment, whereas the catalog 
> file should have been generated by the PostInstall script under 
> /Programs/DocBook-XML-DTD/Current/Resources.
>
> Cheers,
> Lucas
>
> On Sat, Apr 7, 2018 at 3:17 PM, Robert Alexander <sheve...@gmail.com> wrote:
>
>> I myself never have a problem with GCC. If GCC is still available,
>> and you did not remove anything, then things should compile fine.
>> So the error may be elsewhere - what is the specific error that
>> you get?
>> The error I am stuck with right now is in regards to docbook*. I hate
>> that package with a passion... unfortunately it is needed for e. g.
>> dconf, which is in turn needed for gnome-terminal.
>> I settled for mate-desktop myself. It's pretty lightweight and I managed
>> to compile it fine.
>> PS: One of the biggest advantages of GoboLinux is that you can
>> have multiple versions just fine; I recommend to have a static
>> busybox, a few GCC, binutils, coreutils, grep, sed awk (ideally
>> static if possible) - this should help get things compiling reliably.
>> PSS: That "configuration error", whatever it is, should also not happen.
>> If you can reproduce it, please also report it so that it can eventually
>> be fixed. Hopefully. :) (Or documented in the wiki, if we know what
>> happened, and how to resolve it then.)
>>
>> On Mon, Apr 2, 2018 at 5:26 AM, Mason Mullins <masonmull...@protonmail.com> 
>> wrote:
>>
>>> Hello,
>>>
>>> I just installed Gobolinux. I was attempting to update the system and ran 
>>> into a problem.
>>>
>>> I updated the Linux package, Scripts, and Compile as indicated by Freshen. 
>>> I did each one at a time. I then attempted to update GCC but it fails with 
>>> a configuration error and nothing else will compile after that, even when 
>>> setting GCC Current to the original version.
>>>
>>> Was there something I should have updated prior to GCC?
>>>
>>> Mason
>>>
>>> Sent from ProtonMail mobile
>>>
>>> _______________________________________________
>>> gobolinux-users mailing list
>>> gobolinux-users@lists.gobolinux.org
>>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
>>
>> _______________________________________________
>> gobolinux-users mailing list
>> gobolinux-users@lists.gobolinux.org
>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
_______________________________________________
gobolinux-users mailing list
gobolinux-users@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-users

Reply via email to