The solution is to include the LAPACK subroutine and dependencies (subroutines that are called by the main one, those called by these, etc.) in a single .f file. This file is not a module or a program unit of any kind, it's just a text file that contains all subroutines in no particular order, one after the other.
One must be careful because LAPACK often misses dependencies in the .tgz file that is supposed to contain them. There is a network where every subroutine is discussed, and where a map of dependencies can be found, to be found here: http://www.netlib.org/lapack/explore-html/. Check to see if ALL called subroutines are present, and if they are, put them all in one file to make for a simpler compiling command. Also, alter the main code so that all arguments are declared and considered in the main program. The arguments of every subroutine are described in the above network, so they are easily identifiable.
If using gfortran, compile the .f file as an .o object file. This acts as a sort of f77 module which contains all necessary subroutines. It is done through the following command:
gfortran -c filename.f
-c indicates that the file will be compiled as an object file. It is important that all subroutines written in FORTRAN 77 be in a file that is separate from everything written in f90.
There is no need for any "use" statements, as no actual FORTRAN module is being used. Call the necessary subroutines where necessary without worrying about this.
The command for compiling considers the object file as the linked library:
gfortran filename.o progname.f90
This explanation is very distilled and surely most of you know this already, but it was a newbie question that took many hours of research due to things that are not clearly explained in the literature. It is for my own future reference and hopefully it will help other beginners aswell.