It's not quite that simple.
The purpose of the GPL is to provide what the Free Software Foundation sees as the "freedoms" that they believe are essential in all open source software. A program is "free software" if the program's users have the four essential freedoms:
- The freedom to run the program as you wish, for any purpose.
- The freedom to study how the program works, and change it so it does your computing as you wish. Access to the source code is a
precondition for this.
- The freedom to redistribute copies so you can help your neighbor.
- The freedom to distribute copies of your modified versions to others. By doing this you can give the whole community a chance to
benefit from your changes. Access to the source code is a precondition
When the FSF says that "access to the source code is a precondition," that means access to all of the source code. More specifically, it means access to your source code.
So the GPL includes a Copyleft provision that states that, if you use a GPL library in your application and distribute it, then your entire application must be GPL. In practice, that means that you must provide the source code for your entire application.
Simply telling folks that you can get the GPL components elsewhere is not a satisfactory workaround, especially if the GPL components are a required part of your software; in other words, your software won't work without the GPL libraries or code. This is what the FSF calls a combined work. Linking a GPL'd library statically or dynamically with other modules is making a combined work based on that library. Thus, the terms and conditions of the GNU General Public License cover the whole combination.
Assuming that your MIT licensed library contains no GPL'd components or links to any such components, the responsibility of license compliance rests with the user of your library, not you.