[blfs-dev] Xorg Protocol Headers: make?

Fernando de Oliveira famobr at yahoo.com.br
Fri Aug 23 14:14:39 PDT 2013


Em 23-08-2013 09:22, Ken Moffat escreveu:> On Fri, Aug 23, 2013 at
09:15:46AM -0300, Fernando de Oliveira wrote:
>> I have a doubt about the instructions (might have asked before, but
>> cannot remember):
>>
>> Instructions are:
>>
>> ...
>>   ./configure $XORG_CONFIG
>>   as_root make install
>> ...
>>
>> Should not be (as I am using):
>>
>> ...
>>   ./configure $XORG_CONFIG
>>   make
>>   as_root make install
>> ...
>>
>> If not I will change my script, so I will not forget anymore.
>>
>> Thanks in advance for any reply.
>>
>  Running both configure and make as a user would be consistent with
> what we do almost everywhere else.  For at least 99% of all available
> packages which use CMMI, running just configure and make install will
> build the required things on the way to installing them.
>
> ĸen
>

Yes, I was more thinking about consistency.

Em 23-08-2013 12:47, Ken Moffat escreveu:
> On Fri, Aug 23, 2013 at 07:26:14AM -0500, Bruce Dubbs wrote:

...

>> I don't think so.  What does make do for you?  The protocol headers are 
>> just copied to the destination AFAIR.

OK, understood.

>>
>> In mot cases, make install will do a make for you if it's not already done.
>>
>>    -- Bruce
>  Yes, you are right.  I'd forgotten the headers did so little.
> 
> ĸen
> 

Thank you very much, ĸen and Bruce,

Changed the script, which now also have a mention to your replies.

I am waiting for qt to download. It is so much to do, to get a working
desktop environment. And I am in a hurry, to get in position to update
book's tags (at least OJDK, SANE and Xsane). I want this system to
become my main host and main guest (need both), but just for myself, I
would not have to rush...

Now, I am waiting qt:

Saving to: 'qt-everywhere-opensource-src-4.8.5.tar.gz'

29% [+=========>                            ] 70,044,968   255KB/s  eta
22m 19s

Called yesterday my ISP, and they swear that my connection is OK...

-- 
[]s,
Fernando



More information about the blfs-dev mailing list