This is the mail archive of the
mailing list for the Cygwin project.
Re: Aw: Re: Strange errors with gcc and top, even after rebaseall
- From: cyg Simple <cygsimple at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 27 Aug 2017 09:43:40 -0400
- Subject: Re: Aw: Re: Strange errors with gcc and top, even after rebaseall
- Authentication-results: sourceware.org; auth=none
- References: <trinity-28ebbc2f-8902-45b1-aebd-ea52cc253f3b-1503524348648@3c-app-webde-bap32> <firstname.lastname@example.org> <trinity-8fb62eb2-5a08-4f3e-99c6-34baa3379f86-1503559000977@3c-app-webde-bap09> <email@example.com> <trinity-4b3f3381-770b-4c01-b7e1-d7b2d13fadf6-1503688015951@3c-app-webde-bs25> <877exqtfmn.fsf@Rainer.invalid> <trinity-7b987106-f557-41b8-870b-b254245f3676-1503784312569@3c-app-webde-bap64>
On 8/26/2017 5:51 PM, nobodyO@web.de wrote:
>> I guess I don't understand why you thoink you'd need two installations
>> for two build environments.
> I have installed one Cygwin installation package from department A, for
> building software a, and another from department B and which has some
> tools which were developed here, for building software b.
You only need one Cygwin install and the self developed tools reside
within that install; I'll call Cygwin and your tools (TOOLS). Your
source for each department is separated by projects.
You set your PATH to point to your TOOLS. You change to a project
directory and issue the project build command (MAKE). Once the project
is successfully built you create a package to deliver (MAKE package).
There may be reasons to have multiple environments of Cygwin but those
environments must be totally separate and the reasons should only be if
there are differences in the Cygwin environment that are required for a
specific job. What you've presented doesn't appear to be a required reason.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple